Scribd
Upload
26 views

7 Final Report

This document outlines the sections and requirements for a final software engineering project report. It includes sections for an executive summary, project management plan, requirements specifications, architecture, design, and test plan. The project management plan section requires descriptions of the project organization, lifecycle model, risks, resources, schedule, and standards. The requirements section requires use case and non-functional requirements modeling. The architecture section requires documentation of the styles, models, and technologies used. The design section requires GUI, class, sequence, and traceability documentation. The test plan requires test cases traced to requirements and use cases along with a test assessment.

Uploaded by

DR. DILLIP ROUT
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
26 views

7 Final Report

This document outlines the sections and requirements for a final software engineering project report. It includes sections for an executive summary, project management plan, requirements specifications, architecture, design, and test plan. The project management plan section requires descriptions of the project organization, lifecycle model, risks, resources, schedule, and standards. The requirements section requires use case and non-functional requirements modeling. The architecture section requires documentation of the styles, models, and technologies used. The design section requires GUI, class, sequence, and traceability documentation. The test plan requires test cases traced to requirements and use cases along with a test assessment.

Uploaded by

DR. DILLIP ROUT
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

SE 4485 Software Engineering Project

Final Report
Title Page

Executive Summary

Table of Contents
List of Figures
List of Tables

1. Introduction

1.1. Purpose and Scope


1.2. Product Overview (including capabilities, scenarios for using the product, etc.)
1.3. Structure of the Document
1.4. Terms, Acronyms, and Abbreviations

2. Project Management Plan

2.1. Project Organization


2.2. Lifecycle Model Used
2.3. Risk Analysis
2.4. Hardware and Software Resource Requirements
(Do not forget to describe what new software or hardware each team member learned
during the project)
2.5. Deliverables and Schedule
2.6. Monitoring, Reporting, and Controlling Mechanisms
2.7. Professional Standards
2.8. Evidence all the artifacts have been placed under configuration management
2.9. Impact of the project on individuals and organizations
(Include a description of what impact your project will have on individuals and society)

3. Requirement Specifications

3.1. Stakeholders for the system


3.2. Use case model
3.2.1. Graphic use case model
3.2.2. Textual Description for each use case
3.3. Rationale for your use case model
3.4. Non-functional requirements

4. Architecture

4.1. Architectural style(s) used


4.2. Architectural model
4.3. Technology, software, and hardware used
4.4. Rationale for your architectural style and model

1
5. Design

5.1. GUI (Graphical User Interface) design


5.2. Static model – class diagrams
5.3. Dynamic model – sequence diagrams
5.4. Rationale for your detailed design model
5.5. Traceability from requirements to detailed design model

6. Test Plan

6.1. Requirements/specifications-based system level test cases


6.2. Traceability of test cases to use cases
6.3. Techniques used for test generation
6.4. Assessment of the goodness of your test suite
(Which metrics were used for such assessment?)

Acknowledgment

References
(Must be complete, correctly formatted using the standard for IEEE Conference Proceedings)

You might also like