1_ReqAnalysisDesignMod - 1 Requirement Analysis...

Info iconThis preview shows pages 1–9. Sign up to view the full content.

View Full Document Right Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: 1 Requirement Analysis & Design Modeling 2 Quality Function Deployment Function deployment determines the value (as perceived by the customer) of each function required of the system Information deployment identifies data objects and events Task deployment examines the behavior of the system Value analysis determines the relative priority of requirements 3 Activity Diagram for Eliciting Requirements Us e Q FD t o p rio rit iz e re q u ir e m e n t s in f o r m a lly p r io rit iz e re q u ire m e n t s f o rm a l p r io r it iz a t io n ? Cre a t e Us e -c a s e s y e s n o El i c i t re q u i re m e n t s w rit e s c e n a rio d e f in e a c t o rs c o m p le t e t e m p la t e d ra w u s e -c a s e d ia g ra m Co n d u c t FA ST m e e t in g s Ma k e lis t s o f f u n c t io n s , c la s s e s Ma k e lis t s o f c o n s t ra in t s , e t c . 4 Elicitation Work Products a statement of need and feasibility. a bounded statement of scope for the system or product. a list of customers, users, and other stakeholders who participated in requirements elicitation a description of the systems technical environment. a list of requirements (preferably organized by function) and the domain constraints that apply to each. a set of usage scenarios that provide insight into the use of the system or product under different operating conditions. any prototypes developed to better define requirements . 5 Building the Analysis Model Elements of the analysis model Scenario-based elements Functionalprocessing narratives for software functions Use-casedescriptions of the interaction between an actor and the system Class-based elements Implied by scenarios Behavioral elements State diagram Flow-oriented elements Data flow diagram 6 CASE tools Upper CASE tools: support for the analysis and design Lower CASE tools: support for construction and maintenance 1980s Nowadays Integrated CASE tools: Offer extensive life cycle coverage 7 Short for C omputer A ided S oftware E ngineering, a category of software that provides a development environment for programming teams. CASE systems offer tools to automate, manage and simplify the development process. These can include tools for: Summarizing initial requirements Developing flow diagrams Scheduling development tasks Preparing documentation Controlling software versions Developing program code Various companies offer CASE software capable of supporting some or all of these activities. While many CASE systems provide special support for object-oriented programming , the term CASE can apply to any type of software development environment. 8 CASE tools: Automated Diagram Support Checks for syntactic correctness Data dictionary support Checks for consistency and completeness Navigation to linked diagrams Layering Requirements traceability Automatic report generation System simulation Performance analysis 9...
View Full Document

This note was uploaded on 09/21/2009 for the course CSCI CSCI-380 taught by Professor Ahktar during the Spring '09 term at New York Institute of Technology-Westbury.

Page1 / 91

1_ReqAnalysisDesignMod - 1 Requirement Analysis...

This preview shows document pages 1 - 9. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online