Java Installation Issues and Run Types
Java Installation Issues and Run Types
CBSC4103
DR. MARIAYEE DORAISAMY
TOPIC 1
01 Software Crisis
Get a modern PowerPoint Presentation that is beautifully designed. I hope and I believe
that this Template will your Time.
05 Modeling Techniques
Structured Modeling and Object Oriented Modeling
SOFTWARE
C R I S I S
Projects running over-budget
Projects running over-time
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
Gather business and Develop the system, Maintain the system (types
system requirements perform UAT, FAT, of maintenance corrective,
by producing BRS, PAT, WAF testing and adaptive, preventive and
WBS, SRS and etc. verification perfective)
(including functional
and non-functional
testing)
Requirement Characteristics
Complete Consistent and Non- redundant
A requirement should be specified for all conditions that can Each requirement should be expressed only once and should not
occur overlap with another requirement
Consistent
Unambiguous There should not be any conflicts between the requirements.
There should be only one way to interpret the requirement.
Sometimes ambiguity is introduced by undefined acronyms
Understandable
Requirements should be grammatically correct and written in a
Testable (verifiable) consistent style. Standard conventions should be used. The word
“shall” should be used instead of “will,” “must,” or “may.”
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 Feasible (realistic, possible)
unambiguous. The requirement should be doable within existing
constraints such as time, money, and available
Clear (concise, terse, simple, precise) resources
Requirements should not contain unnecessary
verbiage or information. They should be stated
clearly and simply
ENTITY ATTRIBUTE
Add TextPROCESS
Add Text
A B
Login Verify
STUDENT 1 DATABASE / TABLE STUDENT
Login
DATABASE / TABLE
Registration REGISTRATION
Confirmation by
email
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
Thank You