




























































































Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Community
Ask the community for help and clear up your study doubts
Discover the best universities in your country according to Docsity users
Free resources
Download our free guides on studying techniques, anxiety management strategies, and thesis advice from Docsity tutors
analyasis of software
Typology: Exams
1 / 106
This page cannot be seen from the preview
Don't miss anything!
Requirements Analysis: “What” and “How”? (^) Unified Process (^) OO Analysis and Design (^) Basics (^) UML (^) Actors, Use cases
Requirements Analysis [2]
(^) C-: Customer wants and needs; expressed in language understood by the customer. (^) D-: For the developers; may be more formal.
Requirements Analysis [3] Why document requirements?
Requirements Analysis [5] (^) C-requirements: (^) Use cases expressed individually and with a use case diagram. A use case specifies a collection of scenarios. (^) Sample use case: Process sale. (^) Data flow diagram : (^) Explains the flow of data items across various functions. Useful for explaining system functions. [Example on the next slide.] (^) State transition diagram : (^) Explains the change of system state in response to one or more operations. [Example two slides later.] (^) User interface : Generally not a part of requirements analysis though may be included.
Data Flow Diagram Get employee file Total pay Deduct taxes Net pay Issue paycheck Regular hours Overtime hours ID Worker Check Company records Employee Record Tax rates Pay rate Weekly
Overtime rate
Requirements Analysis [6] (^) D-requirements: (^) Organize the D-requirements. (^) Create sequence diagrams for use cases: (^) Obtain D-requirements from C-requirements and customer. (^) Outline test plans Inspect (^) Validate with customer. (^) Release:
Organize the D-requirements: Functional requirements The blood pressure monitor will measure the blood pressure and display it on the in-built screen. Non-functional requirements Performance The blood pressure monitor will complete a reading within 10 seconds. Reliability The blood pressure monitor must have a failure probability of less than 0.01 during the first 500 readings.
Properties of D-requirements: (^) Traceability: Functional requirements D-requirement inspection report design segment code segment code inspection report test plan test report (^) Traceability: Non-Functional requirements (a) Isolate each non-functional requirement. (b) Document each class/function with the related non-functional requirement.
Requirements Analysis [10] (^) Testability It must be possible to test each requirement. Example? (^) Categorization and prioritization..next slide
Requirements Analysis [11] (^) Completeness Self contained, no omissions. Error conditions State what happens in case of an error. How should the implementation react in case of an error condition?
(^) Different requirements must be consistent. R5.4: When the vehicle is cruising at a speed greater than 300 mph, a special “watchdog” safety mechanism will be automatically activated. Example: R1.2: The speed of the vehicle will never exceed 250 mph.
What is Analysis and Design? Analysis - investigation of the problem (what); (^) Design - conceptual solution to fulfill the requirements (how); how will the system do what it is intended to do. (^) What does the system do? (^) Investigation of the problem. (^) What (conceptual) solution will full the requirements
What is OO analysis and design? (^) Essence of OO analysis - consider a problem domain from the perspective of objects (real world things, concepts) (^) Essence of OO design - define the solution as a collection of software objects (allocating responsibilities to objects)