Wähle die Ordner aus, zu welchen Du "ESE Intro" hinzufügen oder entfernen möchtest
0 Exakte Antworten
37 Text Antworten
0 Multiple Choice Antworten
Karte wurde gelöscht
Why Software Engineering?
—Where did the specification come from?
—How do you know the specification corresponds to the user’s needs?
—How did you decide how to structure your program? —How do you know the program actually meets the specification? —How do you know your program will always work correctly? —What do you do if the users’ needs change?
—How do you divide tasks up if you have more than a one-person team?
What is Software Engineering?
State of the art of developing quality software on time and within budget
Multi person construction of multi version software
Software engineering is different from other engineering disciplines (not constrained by physical law)
(Engineering practices cover not only technological aspects of the products being built, but also such diverse aspects such as planning, process management, and quality standards.
Analysis: Model annd specify the requirements ('what')
Design: Model and specify a solution ('how')
Implementation: Construct a solution in a software
Testing: Validate the solution against the requirements
Maintenance: Repair defects and adapt the solution to new requirements
(these are ongoing activties not sequential phases)
Why is the waterfall model unrealistic? What are the problems?
- Because requirements must be frozen too early in the life cycle
- Because requirements are validated too late
Iteration always occurs
Difficult to state all requirements explicitly at the beginning of the project
There won't be a working version of the software until late in the project
(Early prototyping helps to alleviate 2 and 3)
Why Iterative Development?
New requirements can be introduced at any point in the project. Implementation of prototypes may start before detailed design to explore requirements. Testing typically starts as implementation starts.
Plan to iterate your analysis, design and implementation
(You won't get it right the first time, so integrate, validate, test)
(You should only use iterative development on projects that you want to succeed)