- Jan 27th. RJB generated the missing Domain Model graphic. and added UCs.
- Jan 22nd. RJB drew first domain model.
- Jan 21st. RJB explained the problem to the class and elicited first use case.
RJB initiated file with glossary.
. . . . . . . . . ( end of section Blog) <<Contents | End>>
A piece of software that will rapidly organize the accumulated questions and answers
[ Use Case 1 ]
for a topic in this course.
(UC1Name): organize FAQs
(UC1Primary actor): me -- faculty, harassed, confused.
- user gives file name and system finds it.
- system sorts the file by page number (Risk1)
- user reviews result
- system publishes result
Are UC2,3,4 too detailed? All parts of a larger Usecase.
(rapidly): Some response in a tenth of a second, complete reorganization within
5 seconds in 99.9% of cases.
(Risk1): Is the format consistent for page numbers? Answer: NO.
A set of FAQs contain many FAQ, and each FAQ has a headline and a number
(0 or more) other lines.
- FAQ::glossary="Frequently Asked Question".
- FAQ::data=headline #nonheadline.
- FAQs::= #FAQ, any number of FAQ.
- headline::= ". " line.
- nonheadline::= line ~ headline.
- line::= #(char~eoln) eoln.
[ http://cse.csusb.edu/dick/maths/ ]
. . . . . . . . . ( end of section Example Winter 2010 -- How to organize The Frequently Asked Questions on this site) <<Contents | End>>
- Artifact::="Anything that is created in the course of a project".
- artifact::=see above.
- DCD::diagram="Design Class Diagram", shows the classes that will be implemented in code.
- Deliverables::="A packet of artifacts that must be prepared by a deadline for review or distribution".
- Glossary::= See http://cse.csusb.edu/dick/cs375/uml.glossary.html.
- GoF::="Gang of Four",
[ patterns.html#GoF ]
- GRASP::patterns="General Responsibility Assignment Software Patterns",
a set of guidelines for designing objects and classes. They take a single
event that the system must handle and determine a good class to carry it out.
[ patterns.html#GRASP -- General Responsibility Assignment Software Patterns ]
- Grades::= See http://cse.csusb.edu/dick/cs375/grading/.
- KISS::Folk_law="Keep It Simple, Stupid", in agile processes this means never
drawing a diagram or preparing a document that doesn't provide value
to the clients and stakeholders. In all processes it means never
designing or coding what is not needed, see YAGNI.
- OOAD::="Object-Oriented Analysis and Design", See chapter 1 in text.
- patterns::="Documented families of problems and matching solutions", see
- Patterns::= See http://cse.csusb.edu/dick/cs375/patterns.html.
- Process::="How to develop software".
- RJB::=The author of this document,
RJB="Richard J Botting, Comp Sci Dept, CSUSB".
- RUP::Process="Rational UP", a proprietary version of UP.
- SSD::="System Sequence Diagrams", see chapter 10.
- TBA::="To Be Announced".
- UML::="Unified Modeling Language".
[ Unified_Modeling_Language ]
- UP::="Unified Process", an iterative, risk-driven, and evolutionary way to develop OO software.
- YAGNI::XP="You Ain't Gonna Need It", an XP slogan that stops you
planning and coding for things that are not yet needed. As
a rule the future is not predictable enough to program a feature
until the stakeholders actually need now. In this class it also means
"It won't be on the final or in quizzes".
- XP::="Extreme Programming", the ultimate iterative, code-centric, user-involved