Analysis and Design in the Software Development Process
1 of 22
Waterfall Development Process
Move from phase to phase. Not moving to the next phase until you finish current phase.
2 of 22
V-Model Development Methodology
Emphasizes system quality throughout development.
3 of 22
Iterative Development Methodology
Develop system in series of incremental versions
4 of 22
Systems Analyst Role:
1. Analyse business situation. 2. Identify opportunities for improvements 3.Designing information system which supports the business.
5 of 22
What is system analysis?
Identifying main concepts in problem domain and its inter relations. Describe domain in models.
6 of 22
Model
An abstract representation of a system or thing
7 of 22
Design
The process of making a decision about something youre going to create.
8 of 22
Relation between Modeling and Design.
A model is used to understand and reason the domain which leads to the creation and the adaptation of the design.
9 of 22
Abstration
The process of focusing on the important charecteristics of a stitation/object. Ignoring the unessential stuff.
10 of 22
Probelm Domain
The realm of the real world that consists of concepts and relations between them. The problem domain scopes a problem area. A domain model is used to describe ‘what the problem area is’
11 of 22
Solution Domain
The realm of technical means to construct a solution for a problem.
12 of 22
Differences between PD and SD
PD is declarative, describing ‘what’, SD is ‘constructive’ describing ‘how’
13 of 22
Domain Analysis
Domain analysis is the process of identifying, collecting, organizing, analysing, and representing a domain model
14 of 22
What makes a good analysis
Correct Scope, Complete, Consistent, Systematic.
15 of 22
UI
What the user sees e.g forms, Screen etc.
16 of 22
Application Logic
The logic like the controller
17 of 22
Domain
Is like the data holder
18 of 22
Technical Services
Service provider. What interact with the system such as Databases.
19 of 22
Design Principle
Guide or rule to follow for building a solid design.
20 of 22
E.g of design principles:
Creator, Information Expert, Low Coupling, Controller, High Cohesion, Indirection, Polymorphism, Protected Variations, Pure Fabrication.
21 of 22
Design Pattern
a reusable solution for a common problem.
22 of 22
Other cards in this set
Card 2
Front
Move from phase to phase. Not moving to the next phase until you finish current phase.
Back
Waterfall Development Process
Card 3
Front
Emphasizes system quality throughout development.
Back
Card 4
Front
Develop system in series of incremental versions
Back
Card 5
Front
1. Analyse business situation. 2. Identify opportunities for improvements 3.Designing information system which supports the business.
Comments
No comments have yet been made