Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Scribd
Upload
27 views

Module 4: Requirement Determination: Trần Đình Quế, Ph.D, Assoc. Prof

This document discusses approaches to software development and requirement determination. It outlines three principles for object-oriented development: use-case driven, architecture-centric, and iterative and incremental. The document then describes the steps in requirement determination, including defining actors and use cases, drawing diagrams, writing scenarios, and building a glossary.

Uploaded by

anhtrungxd1998
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
27 views

Module 4: Requirement Determination: Trần Đình Quế, Ph.D, Assoc. Prof

This document discusses approaches to software development and requirement determination. It outlines three principles for object-oriented development: use-case driven, architecture-centric, and iterative and incremental. The document then describes the steps in requirement determination, including defining actors and use cases, drawing diagrams, writing scenarios, and building a glossary.

Uploaded by

anhtrungxd1998
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 15

Module 4: Requirement

Determination
Trần Đình Quế, Ph.D, Assoc. Prof.
tdque@yahoo.com
Contents

• Approaches in software development


• Three principles for OO software development
• Analysis Modeling
• Steps in requirement determination
Approaches
in software development
• Based on business processes or data that support
the business.
• A process-centered methodology emphasizes
process models as the core of the system concept.
• Data-centered methodologies emphasize data
models as the core of the system concept.
• Object-oriented methodologies attempt to balance
between process and data by incorporating both into
one model.
Approaches
in software development

• Primary difference between a traditional approach


like structured design and an object-oriented
approach is how a problem is decomposed.
• In traditional approaches, the problem-
decomposition is either process-centric or data-
centric.
• Object-oriented methodologies:
decomposition of problems on class/objects that
contain both data and processes.
Three principles for OO development

According to the creators of the Unified Modeling


Language (UML) [Grady Booch, Ivar
Jacobson, and James Rumbaugh], any object-oriented
approach to developing information systems must be
• use-case driven
• architecture-centric
• iterative and incremental.
Use-case driven

• Use-case driven: use cases are the primary modeling


tools defining the behavior of the system.
• A use case describes how the user interacts with the
system to perform some activity.
-Placing an order
- making a reservation
- searching for information.
• Use cases are used to identify and to communicate the
requirements for the system to the programmers
• Use cases are inherently simple because they focus on
only one business process at a time.
Architecture-centric

• Architecture-centric: the underlying software


architecture of the system drives the specification,
construction, and documentation of the system.
• Object-oriented systems analysis and design approaches
should support at least three separate but interrelated
architectural views of a system:
- functional
- static
- dynamic
Architecture-centric

• Functional/external view describes the behavior of


the system from the perspective of the user.
• Structural/static view describes the system in terms
of attributes, methods, classes, and relationships.
• Behavioral/dynamic view describes the behavior of
the system in terms of messages passed among
objects and state changes within an object.
Iterative and Incremental

Modern object-oriented systems analysis and design


approaches emphasize iterative and incremental
development that undergoes continuous testing and
refinement throughout the life of the project.
Terms

• Systems development process: moving from the


current system (ofen called the as-is system) to the
new system (of en called the to-be system).
• Analysis: general ideas in the system request
Detailed requirement
functional models
structural models
Behavioral models
System proposal
Requirement determination

• Functional models: describe business processes and the


interaction of an information system with its
environment.
• Two types of models are used to describe the
functionality of OO system:
- use cases
- activity diagrams.
• Use cases are used to describe the basic functions of the
information system. Activity diagrams support the
logical modeling of business processes and workflows
Requirement Determination

• Business model
//Modeling the current systems (as-is system)
• System model
//modeling future system (to-be system)

Refer Chapter 3:Tran Dinh Que


Steps in requirement determination

1. Define actors & use cases


2. Draw use case diagram
3. Write scenarios
4. Draw activity diagram
5. Draw sequence/communication diagram
(option)
6. Sketch interface
7. Build Glossary

You might also like