1. Software Engineering
Summarized Slides

2. Waterfall vs. Incremental
Structured…Step by step
Increments….Versioning….Continious Improvement
Phases….Formulae….. (ADIT)
Analysis….Design..Implementation….Testing

3. Analysis Procedure Oriented Object Oriented
ER Diagram (Databases…Entities and Rel:)
Use Case Diagram (actors and usecases)
State Diagram (state of change of entities in response to events)
Class Diagram (Main classes)
Data Flow Diagram (flow of data…symbols—Circle (processing)…Rectangle(source/destination)…open rectangle(data store)….)
State Chart diagram (for every Class)

4. Design Procedure Oriented Object Oriented Structure Charts
Detailed Class diagram…(attributes and methods)
Modularity (Structure charts defines modules) …Cohesion…Needed…Coupling..not needed / minimized

5. Implementation Which programming Language to use…. Procedure Oriented
Object Oriented
C, fortran, c++,Pascal, Basic
Java, C#, c++,
Procedural
Object-oriented
procedure
method
record
object
module
class
procedure call
message

6. Implementation

7. Testing Phase

8. DOCUMENTATION
For software to be used properly and maintained efficiently, documentation is needed. Usually, three separate sets of documentation are prepared for software:
User Documentation
To run the software system properly, the users need documentation, traditionally called a user guide, that shows how to use the software step by step. User guides usually contains a tutorial section to guide the user through each feature of the software.
System Documentation
Document that tells how the software can be maintained and modified by people other than the original developers.
Technical Documentation
describes the installation and the servicing of the software system