Previous page

Next Page

Inception: Get Requirements

Inception: the start-up phase

Getting Requirements- the principle activity in Inception phase
Use Cases are the main vehicle for getting requirements

Obtaining Use Cases

Identify the system boundary (in the surrvey-making project, it's the software application)
Identify Actors & Goals in the application
- (The focus here is on actor intent, not on specifics of user interface)
- Actors and Goals shown below:

Actor	Goal
Survey Maker	Make a survey while online Modify a survey already made After survey preparation, evaluate progress of survey data collection Evaluate final data- get statistics and charts as needed
Survey Taker	Fill out the survey online
Remote Computer	Do whatever User (Survey Maker or Survey Taker) wants to do
System Administrator	Respond to Survey Maker’s problems by answering questions, fixing technical problems Respond to Survey Taker’s problems by answering questions, fixing technical problems Prepare data for use by Survey Maker Maintain database of survey questions and responses Do other system maintenance
Boss Of Sys Admin	Wants everything to work properly for Survey Maker
Supporting Server Processes	Supply required services to software application (may or may be on the same specific server)

Write Uses Cases - one per goal
For larger projects, UML Sequence diagrams made often in inception phase to show rough workflow- assists transition to later Design sequence)