Академический Документы
Профессиональный Документы
Культура Документы
1
Modeling
• ER diagram
• Functions
• ..
3
OORE
• Object-Oriented RE (OORE)
– Classes
– Objects
– States
– Generalization
– Inheritance
–…
4
SOA
• Service-Oriented Architecture
• Services - core artifacts
• Published and Discovered
– Producer centric
– Consumer centric
– Broker centric
5
Conceptual model of SOA
6
SOA…
7
SORE…
• Focuses
– identifying services and workflows,
9
SORE…
• Service
– identification,
– classification
– categorization,
• subsystem analysis,
• component specification,
• Service realization.
10
11
12
GORE
• Goals : artifacts
• A goal is a prescriptive statement of intent
that the system should satisfy through the
cooperation of its agents
• An agent is an active system component
playing a specific role in goal satisfaction
– Human agents
– Devices
– Existing SW components
– New SW components
13
GORE…
• Goal types /semantic/
• Behavioural goals
– Prescribe intended system behaviour
declaratively
• Soft goals
– Prescribe preferences among alternative
system behaviours
• Goal Categories /pragmatic/
• Functional goals
• Non-functional goals
14
Prioritizing
Requirements
15
Requirement Priorities
• the most urgent requirements in the first
release
• resource limitations
16
Requirement Priorities…
• Prioritization helps the project
manager
–resolve conflicts,
–plan for staged deliveries, and
–make the necessary trade-offs
17
Requirement Priorities…
• a way to deal with competing demands for
limited resources
• customer expectations are high and timelines
are short
• is critical for timeboxed or incremental
development with tight, immovable release
schedules
• importance and urgency
• customers must indicate which requirements
are needed initially and which can wait
18
Requirement Priorities…
• Establish priorities early in the project
• Achieving consensus among multiple customers
with diverse expectations is even harder
• Customers place a high priority on those
functions that provide the greatest business or
usability benefit
• The developer might also decide to implement
certain lower priority functions early on because
of their impact on the system's architecture
19
Requirement Priorities…
• If all requirements are top priority,
– your project has a high risk of not being fully
successful
20
High, medium, and low approach
• subjective and imprecise
• stakeholders must agree on
• two dimensions: importance and urgency
21
High…
• Medium priority requirements:
– important (the user needs the capability)
– but not urgent (they can wait for a later release).
22
High…
23
Specification
24
Requirements documentation
• Vision and Scope /business requirements/
26
SRS template…
2. Overall Description
2.1 Product Perspective
27
SRS template…
3. System Features
3.x System Feature X
3.x.1 Description and Priority
3.x.2 Related Use cases
3.x.3 Functional Requirements
4. Data Requirements
4.1 Logical Data Model
4.2 Data Dictionary
4.3 Reports
4.4 Data Acquisition, integrity, retention, and disposal
28
SRS template…
5. External Interface Requirements
5.1 User Interfaces
5.2 Software Interfaces
5.3 Hardware Interfaces
5.4 Communications Interfaces
6. Quality Attributes
6.1 Usability
6.2 Performance
6.3 Security
6.4 Safety Requirements
6.x [others]
29
SRS template…
• 7. Internationalization and Localization
Requirements
• 8. Other Requirements
Appendix A: Glossary
Appendix B: Analysis Models /Context diagram, Use
cases, Class diagram, System Model
30
Read
Chapter 10 – Chapter 14
32