Documente Academic
Documente Profesional
Documente Cultură
Objective : To get familiar with basic model used for software engineering.
Pre-Requisite: Knowledge of
• Various phases.
• Process, project.
Theory : Model used is a process model/ linear sequential Model or classic life
cycle model. This contains following phases
• Requirement gathering.
• Requirement analysis.
• Design.
• Coding
• Testing and Maintenance
Sample output: A document of the case study where all the phases are explained in detail.
Assignment 2:
Title : Apply Spiral and Water fall Model for the project.
Objective : To get familiar with the waterfall and spiral model concepts used in
Software engineering.
Pre-Requisite: Knowledge of
• Water Fall Model.
• Spiral Model.
Sample output: A document which contains the differences among water and spiral model
and also explained in detail.
Pre-Requisite: Knowledge of
• Various process models.
1. Introduction
• Goals & Objectives of software (i.e. Project).
2. Information description.
• Problem description
• Information flow
• Hardware interface
3. Functional description
• Process Narrative for each function
4. Design constrains
• Performance Characteristics
• Behavioral Description
• Validation Criteria
Sample output: A SRS document which contains detailed information about each of the
point specified above with reference to the project work undertaken.
Title : Describe E-R Diagram, DFD, CFD and STD for the project
Pre-Requisite: Knowledge of
• Analysis modeling
(e.g.: Data Modeling, Functional Modeling and Behavioral Modeling)
Theory : Analysis model is first technical representation of the system. This model
consists of data dictionary as its core and then followed by four
diagrams, i.e E-R diagrams, data flow diagram, control flow diagram and
State-transition diagram. All these diagrams are part of the functional
model.
Sample output : Description of E-R Diagram, Data Flow Diagram, Control Flow
Diagram and State Transition Diagram for the project undertaken by you.
Assignment 5:
Title : To compute effort using FP oriented estimation Model for the project
.
Objective : To study software estimation in early stages of software development.
Pre-Requisite: Knowledge of
• Project Metrics
• Software measurement
Objective : To get familiar with the design document and it is used after analysis
Phase.
Pre-Requisite : Knowledge of
• Design concepts
• Design methods
Theory : To translate the analysis model into design model related to the
Project undertaken by you.
Assignment 7:
Pre-Requisite : Knowledge of
• Knowledge of various testing techniques.
Theory : Testing begins “in the small” and progresses “to the large”. The early testing
focuses on a single component and applies various testing techniques tests to uncover errors in
program logic and function. After individual components are tested they must be integrated.
Testing continues as the software is constructed. Finally, a series of high order tests are executed
once the full program is operational.
Pre-Requisite : Knowledge of
• Verification
• Validation
Sample output : A document which contains the information about the verification
and validation of the project.
Assignment 9:
Objective : To get familiar with preparing a test document, used after completion
of the testing phase of the project.
Pre-Requisite : Knowledge of
• Testing strategies.
• Manual testing.
• Automation tools.
Sample output : A document which contains the detailed test information about each of
the point specified above.
Assignment 10:
Pre-Requisite : Knowledge of
• Structure UML Diagrams
• Behavior UML Diagrams
Theory :
• Structure UML Diagrams: It represents the structure and is used
extensively in documenting the software architecture of software
systems.
1. Class Diagrams
2. Component Diagrams
3. Object Diagram
4. Composite Structure Diagram
5. Deployment Diagram
6. Package Diagram
7. Profile Diagram
• Behavior UML Diagrams: It represents the behavior of a system
and is used extensively to describe the functionality of software
systems.
1. Activity Diagram
2. Communication Diagram
3. Interaction Overview Diagram
4. Sequence Diagram
5. State Diagram
6. Timing Diagram
Sample output : A document which contains a required combination of diagrams stated
above for the project undertaken by you.
References : Software Engineering, Roger Pressman, McGraw Hill 2nd edition.
Pre-Requisite : Knowledge of
• Software Engineering Principles
• Software Engineering Methods