2 - Phases of Software Engineering - Updated
2 - Phases of Software Engineering - Updated
2 - Phases of Software Engineering - Updated
Analysis
System
Phases of
Design
Software
Validation
Engineering
Evolution
REQUIREMENTS ANALYSIS
• Tasks determining the needs or conditions to meet for a new or
altered product, taking account of the possibility conflicting
requirements of the various stakeholders, such as beneficiaries or
users.
• Eliciting Requirements
• The task communicating with customers and users to determine
what their requirements are. This is sometimes called as
Requirements Gathering.
• Analyzing Requirements
• Determining whether the stated requirements are unclear,
incomplete, ambiguous, or contradictory, and then resolved
these issues.
• Recording Requirements
• Requirements might be documented in various forms, such as
natural-language documents, use cases, user stories, or process
specifications.
REQUIREMENTS ANALYSIS
• Feasibility Study
Functional Requirements
- describe what the system should do.
Example:
1. A user shall be able to search the
appointments lists for all clinics.
Example:
Reliability, response time
Seatwork
Identifythe functional and non-functional
requirements of a library management
system.
SYSTEM DESIGN
• It is the process of defining the elements of a system such as the
architecture, modules and components, the different interfaces
of those components and the data that goes through that
system.
1. Development Team
responsible in making the software
Build/create the software.
Members of the Development
Team
Analyst
Understands the system
System Designer
Definesthe software architecture,
components, modules, interfaces.
Programmer
write codes of the system in a specific
programming language
Tester
reviews faults and errors of the system
People in the Development Effort
2. End – users
used/ utilize the system
• Executive
• Provides finances and initiatives
• Outputs/results
Quality
• Software Quality
• if it is fit for use
Three Perspectives
1. Quality of the Product
- relative to the person analyzing quality.
*end-users
- if it gives what they want and
when they want it, all the time.
* dev’t team
- errors and faults found during the
SE process
Three Perspectives
2. Quality of the Process
- failures of task are avoided
- system development process is improved