chapter04 - Objectives Describe the activities of the...

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

View Full Document Right Arrow Icon
2 Object-Oriented Analysis and Design with the Unified Process Objectives  Describe the activities of the requirements discipline  Describe the difference between functional and nonfunctional system requirements  Describe the kind of information that is required to develop system requirements  Explain the many reasons for creating information system models 3 Object-Oriented Analysis and Design with the Unified Process Objectives (continued)  Determine system requirements through review of documentation, interviews, observation, prototypes, questionnaires, vendor research, and joint application design sessions  Discuss the need for validation of system requirements to ensure accuracy and completeness and the use of a structured walkthrough  Discuss the need for validation of system requirements to ensure accuracy and completeness and the use of a structured walkthrough
Background image of page 1

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

View Full DocumentRight Arrow Icon
4 Object-Oriented Analysis and Design with the Unified Process Overview  Requirements discipline prominent in elaboration phase  Requirements discipline focuses on models ~ Fact-finding ~ Investigation techniques  Analysts need to be familiar with business concern ~ Bring a fresh perspective to a problem ~ Build credibility with users within the organization 5 Object-Oriented Analysis and Design with the Unified Process The Requirements Discipline in More Detail  Focus shifts from defining to realizing objectives  Activities spread over many iterations of UP  Requirements activities linked to other disciplines: ~ design, implementation, and testing  Output of iteration within elaboration phase is working software 6 Object-Oriented Analysis and Design with the Unified Process Figure 4-1 Activities of the Requirements Discipline
Background image of page 2
7 Object-Oriented Analysis and Design with the Unified Process Gather Detailed Information  Analysts need to dialog with users of new system  Analysts should dialog with users of similar systems  Analysts must read documentation on existing system  Develop expertise in business area system will support  Other technical information should be collected ~ Computer usage, work locations, system interfaces, and software packages 8 Object-Oriented Analysis and Design with the Unified Process Define Requirements  Models record/communicate functional requirements  Modeling continues while information is gathered  Process of refining is source of learning for analyst  Specific models built depend on developing system  The UP provides a set of possible model types ~ Some model types satisfy object-oriented requirements ~ Analysts select models suited to project and skill-set 9 Object-Oriented Analysis and Design with the Unified Process Prioritize Requirements  Users tend to request sizeable number of functions  Scarcity of resources limit function implementation  Scope creep: tendency of function list to grow  Scope creep adversely impacts project ~ Leads to cost overruns ~ May also cause implementation delays  Prioritization of functions antidote to scope creep
Background image of page 3

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

View Full DocumentRight Arrow Icon
10
Background image of page 4
Image of page 5
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 08/01/2011 for the course ITEC 000 taught by Professor Asda during the Spring '11 term at Eastern Mediterranean University.

Page1 / 16

chapter04 - Objectives Describe the activities of the...

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

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