1. Specify And Model Reqs Flashcards
Purpose
To analyze, synthesize and refine elicitation results into r&d
Description
When focus of the specify and model activity is on understanding need -> output referred as reqs
When focus of the specify and model activity on a solution -> output referred as designs
The model used to represent reqs, this task also capturing infor about attributes or metadata about the reqs
Specify and model activities related to all reqs types
Inputs
Elicitation results (Any state)
Modeling can begin with any elicitation result and may lead to the need for more elicitation to clarify or expand upon the reqs
Elicitation and modeling may occur sequentially, iteratively or concurrently
Elements 1
- Model reqs
A model is descriptive and visual way to convey infor to a specific audience in order to support analysis, commu, and understanding. Also used to confirm knowledge, identify gap, identify duplicate infor
Modeling format:
- matrices: model reqs complex but uniform structure, can breakdown element and apply to table
Used for: data dictionary, reqs trace or gap, record reqs attribute and metadata
- diagrams: visual, pictorial, representative reqs that complexity and difficult to do with words
Used to define boundaries, categorize, create hierarchies of item, show data and their relationship
Elements 1- model categories
- People and role: represent org, groups of people, role and their relationships within enterprise to the solution
Tech: org modeling, role & permission matrix, SH list map or personas - rational: represent why of the change
Tech: decision modeling, scope modeling, biz model canvas, root cause analysis, biz rule analysis - activity flow: represent sequence of action, events, or a course that may be taken
Tech: process modeling, use cases and scenarios, user stories - capability: model focus on features or function of enterprise or a solution
Tech: biz capability analysis, functional decomposition, prototyping - data and information: model represent the characteristics and exchange of infor in enterprise or solution
Tech: data dictionary, data flow diagram, data modeling, glossary, state modeling, interface analysis
Elements 2
- Analyze reqs
Ba infor is decomposed into components to further examine for:
- anything must change to meet biz need
- anything should stay the same to meet biz need
- missing component
- unnecessary component
- any constraints and assumption impact to component
Level decompose and level detail depend on:
Knowledge and understand of sh
Org standards
Contractual or regulatory obligations
Other factors
Elements 3
- Represent reqs attributes
BA identify information for reqs and their attributes
Also categorized reqs to schema
Difference types reqs may be specific at same time
Category help ensure the reqs are fully understood, set of any type is complete, appropriate traceability between the types
Elements 4
- Implement the appropriate levels of abstraction
Level of abstraction base on type reqs and audience for the reqs, ba approach also influence to level abstraction and model when define reqs
Guidelines and tools
Modeling notations/standards
Modeling tools: software drawing, storing matrix and diagrams
Reqs architecture: reqs and interrelationship among them -> model are complete and consistent
Solution scope: boundaries for the r&d
Reqs life cycle mng tools: software record, organize, share r&d
Techniques
Acceptance and evaluation criteria
Biz capability analysis
Biz model canvas
Biz rule analysis
Concept modeling
Data dictionary
Data flow diagrams
Data modeling
Decision analysis
Functional decomposition
Glossary
Interface analysis
Non function reqs analysis
Org modeling
Process modeling
Prototyping
Role and permission matrix
Root cause analysis
Scope modeling
Sequence diagram
Sh list map or personas
State modeling
Use cases and scenarios
User stories
Stakeholder
Any sh: BA perform themselves or invite some or all sh to participate this task
Output
Reqs(specified and modeled) combination of r&d in the form text, matrix, diagram
