Requirement Gathering Checklist

Mere som dette

MIT SLOAN Courses

af Ash Martin

Leading team

af SITI HAJAR BINTI MOHAMMAD @ MAUNG ZAW SOE 344BA201408F0149

System Engineering

af Hend Khalid

Validity and Reliability

af Kristine Komorowski

Requirement Gathering Checklist

Performance

Can data be filtered out based on access, search criteria or view?

Is archival of old data possible?

Number of objects are displayed in single view?

Is caching/indexing of data required for performance?

No of simultaneous users are going to use this functionality?

Frequnecy and quantity of data creation/modifcation/deletion?

Captured performance targets? e.g. Any UI load,expansion, auto complete,search,reporting,batch processing time

Usability

sorts are provided in all views?

Are global operations provided in global toolbar?

Modal window whereever required

Visual indicator, right icons/images are provided in UI?

Can autocomplete be used instead of search?

No pop-up?

Avoid reload of page.. Refresh page/data silently

Avoid wizards

Easy navigation?

Followed OOTB styles Consistent UI wrt extising WBOM application

Less number of clicks

Impact Analysis

Module Dependancies

Mentioned related use case in other modules?

Enhancement to existing functionality

Change in schema required?

Change in existing UI required?

Any change in existing workflow/functionality?

Any impact on existing functionalities?

Any change is required with other system integrations (EB7,V5,Blackberry)

Change in existing search required?

Change in any background/scheduler job?

Change in reporting required?

Change in any existing UI ?

Change in any existing access rule?

Change in any existing workflow?

List down existing impacting functionalities/modules

Change in existing schema required?

Does it need any data migration?

Functionality

New Intergration required?

Upgrade

Any data migration required from legacy system?

Production downtime

Data Volumn considered?

Metadata /file migration?

Frequency of migration

Bi-direction/uni-directional

Data Cleaning

Schema mapping

Any change in existing integration required (V5,EB7..)?

Any reporting requirement?

Introduction of any global search required?

Mentioned alternate use case flows

Captured screenshots of existing system for reference?

Mentioned UI details including in specified format.

Boundry condition functionalities/use cases are discussed?

Mentioned dependency on other use cases/modules

Mentioned all assumptions

Mentioned access control based on role and workflow

Mentioned proposed functionality flow, data flow, algortihtm?

Mentioned targeted user/roles?

Mentioned business benefits?

Briefed AS-IS and To-Be process?

Mentioned existing pain areas?