Software construction topic 1Topic 1.pdf

Software construction

1. SOFTWARE CONSTRUCTION
CBSC4103

DR. MARIAYEE DORAISAMY

2. TOPIC 1
Get a modern PowerPoint Presentation that is beautifully designed. I hope and I believe
that this Template will your Time.
Software Crisis 01
Waterfall, Spiral, Rapid Application Development, Rational Unified Process and etc.
System Development Methodology 02
Feasibility Study, Requirement Analysis and Specification, System Architecture Design,
Implementation and verification, Installation and Delivery, and Maintenance
Waterfall Life Cycle 03
Get a modern PowerPoint Presentation that is beautifully designed. I hope and I believe that
this Template will your Time.
Software Specification Characteristics 04
Structured Modeling and Object Oriented Modeling
Modeling Techniques 05
https://www.tatvasoft.com/blog/top-12-software-development-methodologies-and-its-advantages-disadvantages/

3. Project often did not meet requirements.
Projects running over-budget
Projects running over-time
Project was very inefficient.
Project was of low quality.
SOFTWARE
C R I S I S
Projects were unmanageable and code difficult
to maintain.
Project was never delivered.
Rapidly increasing in software demand, complexity
of software and software challenges.
With increase in the complexity of software, many
software problems arise because existing methods
were insufficient.

4. Market Research
•The process of gathering, analyzing and
interpreting information about what
customers want.

•The existing need and future needs are
analyzed and interpret in order to get
support customer requirements.

•A detail market research could reduce
software crisis.

5. Next
System Development Methodology

6. Software Development Methodologies
Further Info can refer to https://acodez.in/12-best-software-development-methodologies-pros-cons/
Waterfall Model
Prototype Methodology
Agile Software Development Methodology
Rapid Application Development:
Dynamic System Development Model Methodology
Spiral Model
Extreme Programming Methodology
Feature Driven Development
Joint Application Development Methodology
Lean Development Methodology
Rational Unified Process Methodology
Scrum Development Methodology

7. Waterfall Model
Feasibility
Studies
Installation &
delivery
Design
Requirement
& Analysis
Implementation &
Verification
Gather business and
system requirements
by producing BRS,
WBS, SRS and etc.
(including functional
and non-functional
testing)
Develop the system,
perform UAT, FAT,
PAT, WAF testing and
verification
To Determine cost
and benefit of the
project and make
decision whether
to proceed the
project
Design database, input,
output and overall
interface design
Install the system at user
place and test run. (types of
installation direct, parallel,
phase by phased and pilot)
Maintenance
Maintain the system (types
of maintenance corrective,
adaptive, preventive and
perfective)

8. Requirement Characteristics
Understandable
Feasible (realistic, possible)
Testable (verifiable)
Clear (concise, terse, simple, precise)
Unambiguous
Consistent and Non- redundant
Complete
Each requirement should be expressed only once and should not
overlap with another requirement
Consistent
There should not be any conflicts between the requirements.
Requirements should be grammatically correct and written in a
consistent style. Standard conventions should be used. The word
“shall” should be used instead of “will,” “must,” or “may.”
The requirement should be doable within existing
constraints such as time, money, and available
resources
Requirements should not contain unnecessary
verbiage or information. They should be stated
clearly and simply
Testers should be able to verify whether the requirement is
implemented correctly. The test should either pass or fail. To
be testable, requirements should be clear, precise, and
unambiguous.
There should be only one way to interpret the requirement.
Sometimes ambiguity is introduced by undefined acronyms
A requirement should be specified for all conditions that can
occur
For further explanation can refer to https://www.informit.com/articles/article.aspx?p=1152528&seqNum=4

9. 2
3
4
1
WHY WE NEED TO USE SOFWARE
DEVELOPMENT METHODOLOGY
5
To have Systematic Development
To produce a quality software / project
To make sure all the roles within project
collaborate based on methodology
To monitor and control the software/
project development
To lead software / project success

10. TYPES OF SPECIFICATIONS
Formal - Informal Specification
Textual – Graphical Specification
Operational - Descriptive Specification
Text Based / Natural Language
Construct model ( Physical / Abstract / Mathematic
Equations) and behavior
Graphical
01
02
03
**Try to find the Pro and Cons of each type specification

11. Data Modeling
For the purpose of software development, we can have two types of data modeling which are Structured Modeling
and Object Oriented Modeling.
Entity Relationship Diagram (ERD)
Data Flow Diagram (DFD)
Structured Modeling
Object Oriented Modeling
UML Modeling
Class Diagram

12. Entity Relationship Diagram (ERD)

B
Add Text Add Text
A
ENTITY
Get a modern PowerPoint Presentation
that is beautifully designed.
RELATIONSHIP
ATTRIBUTE
Name Register STUDENT
STUDENT
Name NRIC
Register SUBJECT
SubjectName SubjectCode

13. DATA FLOW DIAGRAM(DFD)

B
Add Text Add Text
A
ENTITY
Get a modern PowerPoint Presentation
that is beautifully designed.
PROCESS
ATTRIBUTE
STUDENT
STUDENT
DATABASE / TABLE Registration
1
Login

2

Registration
DATABASE / TABLE STUDENT
Login
Register Subject
Verify
Confirmation by
email
DATABASE / TABLE SUBJECT
DATABASE / TABLE
REGISTRATION

14. Revision Questions
Topic 1
What is software crisis?
What are problems that can be classified as software crisis?
What is market research?
What is software development methodology?
What are types of Software development methodology?
Why software development team need to use software
development methodology?
What are the phases in software development methodology?
What is feasibility study?
Types of design focuses ?
Types of maintenance?
Specification Requirement Characteristics ?
Structured Approach like DFD and ERD

15. Thank You