s You are here: Home > Development > Requirements analysis > Develop UI prototype
UMP slogan Home | About UMP | FAQ | Discuss | Contacts | Site map
  Life cycle model   Development process   Support process   Organizational process   Product    
Implementation | Analysis | Architecture | Design | Programming & Testing | Integration | Qualification




Analysis tasks:

5.3.4.UMP1 Define Product Business Specifications
5.3.4.UMP2 Collect product requirements
5.3.4.1 Specify software requirements
5.3.4.UMP3 Develop UI prototype
5.3.8.4 Develop test cases
5.3.4.2 Evaluate SRS
5.3.4.UMP4 Evaluate UI prototype
5.3.8.5b Evaluate software test case

 

 

References:

UMP glossary
Bibliography
Conventions & Notation

 

Task 5.3.UMP3: Develop UI prototype

UMP
  Development Process

         Software Requirements analysis Activity
<< previous task | next task >>

 

Task goals

To develop system User Interface model and mockup which users could evaluate.

Rationale:
The UMP requires that the user interface development tasks (external modeling) start concurrently with the software requirements analysis activity and continue in parallel with subsequent development activities. It is too late to develop the user interface if most of the application has been completed.

Procedure
  1. Analyst: Develops user input—output forms for each Actor—UseCase relationship of the Use Case model.
  2. Analyst: Incorporates Quality requirements, applicable to the User Interface model and stated in PBS, into the User Interface model.
  3. Analyst: Incorporates Constraints, applicable to the User Interface model and stated in PBS, into the User Interface model.
  4. Analyst: Analyzes task input Documents and Checklists and makes the necessary changes in Output documents.
  5. Product Manager and Developers: Conduct Technical Review.
  6. Analyst: Publishes SRS.
Inputs Programming artifacts None
Model The Use Case model
Documents
Checklists UI prototype evaluation & verification from the previous iteration
Guides The UI prototyping guide
Outputs Programming artifacts Interactive UI prototype
Model The User Interface Model
Documents UI requirements & design document, External model section
Checklists None
Completion criteria  
Quality metrics  
Milestones  
Task improvement opportunity events
  • Project participants are unable to assess the prototype
  • The prototype has little value for development (no impact on development)

 

 

Last modified: 07-Jan-2005
Copyright © 2003—2005 Alexander Kozlinski. All rights reserved.
Use of this website signifies your agreement to the Terms of Use