DOC PREVIEW
CORNELL CS 501 - CS 501 Lecture Notes

This preview shows page 1-2-14-15-30-31 out of 31 pages.

Save
View full document
View full document
Premium Document
Do you want full access? Go Premium and unlock all 31 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 31 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 31 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 31 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 31 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 31 pages.
Access to all documents
Download any document
Ad free experience
Premium Document
Do you want full access? Go Premium and unlock all 31 pages.
Access to all documents
Download any document
Ad free experience

Unformatted text preview:

CS 501: Software EngineeringAdministrationWeekly Progress ReportRequirements Analysis v. System DesignModels: Useful TextsModelsPrinciples of ModelingThe Unified Modeling LanguageRational RoseDiagrams and Specification in UMLActor and Use Case DiagramUse Cases and ActorsAccessibility ProfileScenarioScenario: a Typical StudentScenario (continued)Slide 17Modeling Scenarios as Use CasesSpecification of Use CaseSpecification of Use Case (continued)Use Case Diagram for Quiz SystemUse Cases for Quiz SystemRelationships Between Use Cases: <<includes>>Relationships Between Use Cases: <<extends>>Use Cases in the Development CycleDocumentation: GeneralDocumentation of Requirements Specification: PurposeRequirements Specification: PurposeSlide 29Requirements Specification: DetailsRequirements Specification: Process1CS 501 Spring 2008CS 501: Software EngineeringLecture 9Requirements II2CS 501 Spring 2008AdministrationQuiz 1If you did not pick it up on Thursday, you can collect your quiz from reception at 301 College AvenueFeasibility StudyComments have been sent to several groups. I plan to have them all sent out by the end of today.3CS 501 Spring 2008Weekly Progress ReportEvery project will be assigned a Teaching Assistant.Weekly progress reports• Every Friday beginning, February22• Send email to Teaching Assistant • Three short sections (total less than one page)-> What has been accomplished in the past week (list of tasks)?-> What is planned for the next week?-> Have any problems arisen?4CS 501 Spring 2008Requirements Analysis v. System DesignDilemma. • Requirements analysis should make minimal assumptions about the system design.• But the requirements definition must be consistent with computing technology and the resources available.In practice, analysis and design are interwoven. However:1. Do not to allow the requirements analysis to prejudge the system design.2. Do not allow assumptions about the design to influence the requirements analysis.5CS 501 Spring 2008Models: Useful TextsGrady Booch, James Rumbaugh, Ivar Jacobson, The Unified Modeling Language. Addison-Wesley 1999.Grady Booch, Object-Oriented Analysis and Design with Applications, second edition. Benjamin/Cummings 1994.Rob Pooley, Perdita Stevens, Using UML Software Engineering with Objects and Components. Addison-Wesley 1999.6CS 501 Spring 2008ModelsA model is a simplification of reality.• We build models so that we can better understand the system we are developing.• We build models of complex system because we cannot comprehend such a system in its entirety.Models can be informal or formal. The more complex the project the more valuable a formal model becomes.BRJ7CS 501 Spring 2008Principles of Modeling• The choice of what models to create has a profound influence on how a problem is attacked and how a solution is shaped. • Every model can be expressed at different levels of precision.• The best models are connected to reality.• No single model is sufficient. Every nontrivial system is best approached through a small set of nearly independent models.BRJ8CS 501 Spring 2008The Unified Modeling LanguageUML is a standard language for modeling software systems• Serves as a bridge between the requirements specification and the implementation.• Provides a means to specify and document the design of a software system.• Is process and programming language independent.• Is particularly suited to object-oriented program development.9CS 501 Spring 2008Rational RoseRational Rose is an IBM-owned system for creating and managing UML diagrams.It is available for Computer Science Department computers.10CS 501 Spring 2008Diagrams and Specification in UMLA diagram is the graphical representation of a set of elements, usually rendered as a connected graph of vertices (things) and arcs (relationships).Each diagram is supported by technical documentation that specifies in more detail the model represented by the diagram.A diagram without documentation is of little value.11CS 501 Spring 2008Actor and Use Case Diagram• An actor is a user of a system in a particular role. An actor can be human or an external system.• A use case is a a task that an actor needs to perform with the help of the system.Borrow bookBookBorrowerUse cases make more precise the concept of viewpoint analysis.12CS 501 Spring 2008Use Cases and Actors• A scenario is an instance of a use case • Actor is role, not an individual(e.g., librarian can have many roles)• Actor must be a "beneficiary" of the use case(e.g., not librarian who processes book when borrowed)In UML, the system boundary is the set of use cases.13CS 501 Spring 2008Accessibility ProfileAccessibilityCreating computer systems that can be used by people with special needs, e.g., poor vision, lack of hearing, disabilities, etc.ProfileA description of a user with special needs, e.g.,• an elderly person with 20/70 vision who is unable to control a mouse• a 20 year old student who is red-green color blind14CS 501 Spring 2008ScenarioA scenario is a tool used during requirements analysis to walk through a specific interaction with a proposed system.ExampleThe requirements are being developed for a system that will enable university students to take quizzes online from their own rooms using a Web browser.Create a scenario for a typical student.15CS 501 Spring 2008Scenario: a Typical StudentIndividual: Philip Glass, senior at Cornell, major in computer science, location Risley Hall.Equipment: Dell laptop attached to Cornell dormitory network. Firefox 2.0 browser and Sidecar authentication system installed.Scenario: 1. PG powers up computer and authenticates using Sidecar.2. PG starts browser and types URL of Quiz system.3. Quiz system displays list of options.16CS 501 Spring 2008Scenario (continued)4. PG selects CS 501 Quiz 1.5. A list of questions is displayed, each marked to indicate whether completed or not.6. PG selects a question and specifies whether he will submit a new answer or edit a previous answer.7. For the first question, he is submitting a new answer. He has a choice whether to type the solution into the browser or to attach a separate file. He decides to attach a file.8. For the second question, he is editing a previous answer. He chooses to delete a solution previously typed into the browser, and to replace it with an attached file.17CS 501 Spring 2008Scenario (continued)9. PG has


View Full Document

CORNELL CS 501 - CS 501 Lecture Notes

Documents in this Course
Quiz 2

Quiz 2

2 pages

Usability

Usability

31 pages

Quiz 1

Quiz 1

2 pages

Stulba;''

Stulba;''

33 pages

Load more
Download CS 501 Lecture Notes
Our administrator received your request to download this document. We will send you the file to your email shortly.
Loading Unlocking...
Login

Join to view CS 501 Lecture Notes and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view CS 501 Lecture Notes 2 2 and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?