Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 4 years ago.
Improve this question
CRC cards are known as one of the simple, intuitive method
to simulate your system before creating it.
Many people praises its goodness with a few of criticism
but I could not find well, solid examples about its actual usage
or good case studies.
YouTube only provides two direct examples how CRC methods
are used - both of them are played in not american, even the
creators of the method are two great american ^^.
How funny?
So here I want to know how many people actually uses CRC in design session?
Is it still valid or great? Is it worth to investigate, practice and put in many hours?
My guess is that this is largely replaced by UML. Never heard of anyone using CRC, but then again I'm more in the web than corporate development..
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
So, I working on a problem at my workplace, that is a big company with a serious CNC shopfloor. Here I thought I could make the life much easier with a little software. I have the conception, I put a lot of work in it together with my helpful friends and here is the point, when I suppose to explain it to my leaders.
The problem is, I've never made anything like this before. So I don't know the way. I should use UML-diagrams and use cases, class diagrams etc? Or which is a preferred way?
Out of the management perspective you could explain why your programm is efficient and required to optimise the workflow. Creating a presentation could help you make the idea of the application clear and bring it in a form which is understandable.
If I were you I will go in priorities for activities diagram. You create an activity diagram of the old flow and another with the new flow. You show both to your manager and you compare them. Normally your program will minimise steps inside the new flow. Then you can say that with less steps to manage there will be more money to earn for your manager and you at the end :)
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I recently started looking at programming and have been quite interested in it. The only bad thing is that I don't know how code works, where I can write it, or what languages to take into consideration.
I want to learn how to make applications for the iOS operating system, and i heard Objective C is the language for that. Is Objective C something you would recommend to a beginner?
I just wish I could grasp the concept of programming a little better and get a better understanding because, as of right now, it seems extremely complicated.
As a beginning programmer, I would advise that you'd be better served learning how computers and programs work as a general concept, which will orient your thinking as to how programs are made.
I've heard lots of good things about the Haskell language in this regard, and I would recommend you start here: http://tryhaskell.org
Once you have a good concept of how programs work, and what kind of thinking and organisation is required, then you can move on to languages like C/Objective-C, which would be very frustrating to start on.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 years ago.
Improve this question
I've witnessed a number of debates regarding this question, and have seen a few inconclusive discussions online as well. The debate just sparked up between students in my Software Architecture and Design course, and I'd like to hear some thoughts from a more knowledgeable perspective.
So my question is simple: Should "logging in" be considered a use case? Is there a definitive answer to this, or is it something that will always welcome debate?
Although I think that here is not a good space for debate, because of the site format and rules, I think this is a valid question. At first I wondered why not considering logging in as a use case. So, I google it and found that enlightening discussion. Now it is clear to me. There is no easy answer. It also depends on the level of the use case modelling. At the requirement eliciting, logging in is not a use case, but at the system design level it might appear as a use case . If security is a concern, it must appear and be treated as a special use case.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
I'm looking for some guidelines on writing a technical spec. This spec will be given to contract programmers for writing the business logic in an application. There is no user interaction in these applications, only application to application interaction. So far I've only been able to find information on writing specifications based on user input. I was thinking that maybe UML would be useful for this, but I'm not sure.
If anyone could point me in the right direction I would appreciate it. Thanks!
My suggestion is; if you doesn't have a lot of time to spend on this make some input/output sketches of the functions combined with UML flow diagrams. If you have time and some money to spend I can recomend "Object-oriented Modelling and Design with UML" by Michael Blaha and James Rumbaugh. read it and apply it on your requirements but instead of going to implementation leave it to the contract programmers. It is more time upfront but less questions later. Hope it helps.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
While studying different programming languages, I recently hit upon Icon programming language. It seems to have quite cool syntax and functions for string scanning, goal directed execution, generators etc. and it was developed quite a few decades back (1977).
There doesn't seem to be much information available on it regarding the places it is used currently. It doesn't seem to be actively developed or supported also. I was wondering if people really use this language in certain niche areas even today or is the language now primarily of historical interest? Will it have much relevance in future also?
The TIOBE programming language index http://www.tiobe.com/index.php/content/paperinfo/tpci/index.html places it somewhere between 50th and 100th in terms of
the number of skilled engineers world-wide, courses and third party vendors.
If it hasn't gotten any further than that since 1977, I doubt it ever will.
If you're into "cool," complex languages with sophisticated capabilities, Scala may scratch your itch.