Thursday, April 18, 2013

Business Requirement Analysis

1. Identify stakeholders(more importantly Killer SH): Compliance, Customer, Resource, Owner/Manager
2. Identify drivers: Problems, Opportunities, Constraints
3. Identify objectives: Should be SMART
4. Change Management:

Context diagram and scope dimension:
1. Locations
2. Processes
3. Applications
4. Organization units
5. Technology
6. Any other
7. Out of scope

Requirements for change:

1. Scope requirement
2. Functional requirement; Priority: Must,Should,Could,Would
3. Detailed requirement

Processes are made around


1. run at Locations
2. Implemented on Applications
3. used by Organization units
4. use Technology
5. execute Business Rules
6. manipulate Data
7. implement Functional requirements

Next step:

Data model
Business process model

Data specification facets:
1. Non-Functional requirement: Access, archive, availability
2. Data content roles
3. Data relationship rules

Actions:

prepare data models(ER/UML)
document data content rules
document data non-functional requirements


Data Model Concepts: Entity Relation Diagram(ERD can be normalized)/Class diagram.

Basic components or ERD:
1. Entity
2. Relationship
        relationship cardinality: Crow Foot/UML class cardinility
3. Attribute





No comments:

Post a Comment