Common Sections for the Documentation Set Each document within the recommended set has some common

characteristics. The following pages are included in each document:

Name of Document

Software Project Management Plan (SPMP)

Project Title

Logo

ISS 1123 Introduction to Software Engineering

Lecturer: Mdm Kamsiah Binti Mohamed Faculty of Computer Science and Information Technology University Selangor Version Draft/Final Primary Author(s) Name Matric Programme No. Description of Version Date Completed

IAS 2133- Software Engineering

Page 1

1. Overview of the Documentation Set The following table identifies the minimal core set of software, and identifies the activities that produce them. Document Description Activities (IEEE/EIA 12207.2-1997) [1] System requirement analysis Software requirement analysis

Deliverables Description of the software approach and associated milestones.

Software Project Management Plan (SPMP)

Software Requirements Specifications (SRS) Software Design Description (SDD)

Description of the expected software features, constraints, interfaces and other attributes. Description of how the software will meet the requirements. Also describes the rationale for design decisions taken. Description of the plan and specifications to verify and validate the software and the results.

Process implementation

System architectural design Software architectural design Software detailed design

Software Test Documentation (STD)

Software qualification testing System qualification testing

IEEE terms and abbreviations have been used throughout; this provides exposure to the professional terminology for students, and also reduces ambiguity.

1.2 Purpose of each document Document SPMP SRS SDD STD Summary of Purpose To document the agreed deliverables and dates. To document the agreed requirements with the project supervisor; to provide the basis for design; to provide the basis for system test. To document the design and design decisions in order to provide the basis for implementation and unit test To document how the software will be tested, and record the results.

IAS 2133- Software Engineering

Page 2

Software Project Management Plan (SPMP)

Cover Page Revisions Page Table of Contents

1.

INTRODUCTION 1.1 1.2 Project Overview Project Deliverables

PROJECT ORGANIZATION 2.1 2.2 2.3 Software Process Model Roles and Responsibilities Tools and Techniques

PROJECT MANAGEMENT PLAN 3.1 Tasks 3.1.1 3.1.2 3.2 Deliverables and Milestones Risks and Contingencies

Timetable

IAS 2133- Software Engineering

Page 3

1.

INTRODUCTION The website for the Project Management Association (PMA) be updated to employ a more dynamic approach with the ability to publish news and events pertaining to project management to the public. 1.1 Project Overview

The site will also allow UNISEL students and alumni to register to access private content. The updated site will permit the UNISEL-PMA to deliver information, possibly coming from different sources, to the users who have access to the private section. As the site is converted to use a dynamic front-end the ability to use social networking components will be available to the community. The user community will be able to communicate with one another, access information stored in multiple locations pertaining to project management, and even be aware of upcoming events and possible job opportunities in the project management field. The budget for the updated UNISEL-PMA site is RM40, 000.00. A hosting investment has been made for this site at RM200 per year. An initial estimate provides a total of 40 hours per week per team. The budget allocated is to be used to cover internal labor costs, software required for development, and any training required to complete the task or educate the community about the update. There is an expectation of ROI within 365 days post delivery. The benefit of updating the site will be the ability to supply the user community a central location to access project management resources instead of having them visit sites external to the UNISEL-PMA. 1.2 Project Deliverables Summary of Project Deliverables: 1. Scope Statement 2. Costs Estimation 3. Work Breakdown Structure (WBS) 4. Schedule 5. Status Reports/Meeting Minutes 6. Final Project Presentation 7. Lessons Learned Product-related deliverables: 1. Developer Documentation: the documentation of required for future developers to continue using the same codebase that will be delivered. 2. User Documentation: the documentation required for site administrators and database administrators. 3. Web Server Configuration: the configuration commands required to get the host site to mirror the configuration of the development site.

IAS 2133- Software Engineering

Page 4

PROJECT ORGANIZATION Diagram of project model to be used for development.

2.1

Software Process Model Project model and rough timeline phase relationship

IAS 2133- Software Engineering

Page 5

2.2

Roles and Responsibilities Team Member Skill Set Management QA, test officer Database Role Project Manager Quality assurance product testing Database lead Responsibilities Remarks Overall project management Oversee overall product quality Overall database development and integration

2.3 design

Tools and Techniques Example : Microsoft Visio/Rational Rose is used to create the project planning and diagram

PROJECT MANAGEMENT PLAN 3.1 Tasks 3.1.1 Deliverables and Milestones

Software Project Management Plan

IAS 2133- Software Engineering

Page 6

Project Milestones

IAS 2133- Software Engineering

Page 7

3.1.2 Risks and Contingencies Schedule Risk: Schedules often slip due to following reasons:
i. ii. iii. iv.

Wrong time estimation. Resources are not tracked properly. All resources like staff, systems , skills of individuals etc. Failure to identify complex functionalities and time required to develop those functionalities. Unexpected project scope expansions

Operational Risks: Risks of loss due to improper process implementation, failed system or some external events risks. Causes of Operational risks:
i. ii. iii. iv. v. vi.

Failure to address priority conflicts. Failure to resolve the responsibilities. Insufficient resources. No proper subject training. No resource planning. No communication in team.

Technical risks: Technical risks generally leads to failure of functionality and performance. Causes of technical risks are:
i. ii. iii. iv.

Continuous changing requirements No advanced technology available or the existing technology is in initial stages. Product is complex to implement. Difficult project modules integration.

Programmatic Risks: These are the external risks beyond the operational limits. These are all uncertain risks are outside the control of the program. These external events can be:
i. ii. iii. iv.

Running out of fund. Market development Changing customer product strategy and priority Government rule changes.

IAS 2133- Software Engineering

Page 8

Software Requirements Specifications (SRS)

Cover Page Revisions Page Table of Contents

INTRODUCTION 1.1 Product Overview

SPECIFIC REQUIREMENTS 2.1 External Interface Requirements 2.1.1 2.1.2 2.1.3 User Interfaces Hardware Interfaces Software Interfaces

2.2 Software Product Features 2.3 Software System Attributes 2.3.1 2.3.2 2.3.3 2.3.4 2.3.5 2.3.6 Reliability Availability Security Maintainability Portability Performance

IAS 2133- Software Engineering

Page 9

Software Design Description (SDD)

Cover Page Revisions Page Table of Contents

INTRODUCTION 1.1 Design Overview 1.2 Requirements Traceability Matrix

SYSTEM ARCHITECTURAL DESIGN 2.1 Chosen System Architecture 2.2 Discussion of Alternative Designs 2.3 System Interface Description

3 4

DETAILED DESCRIPTION OF COMPONENTS USER INTERFACE DESIGN 4.1 Description of the User Interface 4.1.1 4.1.2 Screen Images Objects and Actions

IAS 2133- Software Engineering

Page 10

Software Test Documentation (STD)

Cover Page Revisions Page Table of Contents

INTRODUCTION 1.1 System Overview 1.2 Test Approach

TEST PLAN 2.1 Features to be Tested 2.2 Features not to be Tested 2.3 Testing Tools and Environment

TEST CASES 3.n.1 3.n.2 3.n.3 3.n.4 Purpose Inputs Expected Outputs & Pass/Fail criteria Test Procedure

References [1] IEEE 12207.2-1997 Industry Implementation of International Standard ISO/IEC 12207: 1995 (ISO/IEC 12207) Standard for Information Technology - Software Life Cycle Processes - Implementation Considerations [2] Computing Curricula 2001, The Joint Task Force on Computing Curricula, Final Report, IEEE Computer Society, Association for Computing Machinery, Dec 15, 2001
IAS 2133- Software Engineering Page 11