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.
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 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 4 years ago.
Improve this question
I am documenting a small itcl project. Due to shortcomings in itcl support in doxygen, and the fact that Ruff! does not support itcl, I am left with NaturalDocs and RoboDoc as the leading candidates. However, I don't want to pick an unsupported system, and was wondering which is going to be there in the long term?
What will be there in the long term? Who knows! It depends on how much people use it, really, as with all open source code systems. It should be noted that both the tools you refer to are really slow developing at this point: they do what they do and need little significant change to keep on doing it.
As far as I can see, ROBODoc requires that you do pretty much all the annotation work yourself, whereas NaturalDocs will derive a bit more for you. Not very much though; in particular, you will have to write plenty of annotations on things whichever route you use. (I've no particular experience with either though; I tend to prefer to maintain documentation in a separate file with something like doctools but that's a very different approach. I've also done nasty custom things in the past; you really don't want to use them.)
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..
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I am wondering about how to enable anonymous posting of question and answer in a OSQA website, like stackoverflow.com does. If OSQA does not support this feature yet, can you please give me a short brief on how can I implement a such feature like that?
Currently users, that are not authenticated cannot ask questions, post comments and answers. Actually the whole concept of Q&A community is based on user authorization. Just try to imagine a "community" where the one who asks is unknown (or call him a guest, if you like), and the ones who answer and comment are also unknown users.
Personally I don't think that the registration process is painful. Actually it's maximally simplified and users can get registered in less than a minute. Anyway, will be glad to hear how you think it can be improved.
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
For me it's got to be the Microsoft SQL Server Cast and Convert reference. I must love that page, I seem to visit it several times a day.
PHP Documentation for me - clear, concise, user tips (although these are not always correct and secure - pinch of salt etc). Also good for typing directly into an address bar if you know the function name, eg php.net/in_array - straight to the function's page.
The YUI documentation has had a good number of views over my last few projects...a good example of a clear and concise API
Definitely should be http://www.w3.org/TR/xslt :)
It depends a lot on what I'm doing and what my toolset is. In generaly these days it is probably Stroustrup's The C++ Programming Language.
From time to time, I still find that people need my services maintaining/fixing/adding new features to ASP site (VBScript) pages from time to time (yuck). The MSDN VBScript reference is usually all I need.