Download - BASIL Software Development Plan

NYSS Software Solutions

<Project Name>Software Development Plan (SmallProject)

Version 1.1

Authors – Saqib Abbas & Ndumayak Onomo

Bar Coded Assessment System for Independent Leaning (BASIL) Version: 1.1Software Development Plan (Small Project) Date: 19/11/2010BASIL_Software_Development_Plan.docx

Revision HistoryDate Version Description Author

11/11/2010 1.0 First Release Saqib Abbas

Ndumayak Onomo

19/11/2010 1.1 Final Release Saqib Abbas

Ndumayak Onomo

Confidential NYSS Software Solutions, 2023 of 13


Table of Contents

Contents

1. Introduction...........................................................................................................................................................4

1.1 Purpose...........................................................................................................................................................4

1.2 Scope...............................................................................................................................................................4

1.3 Definitions, Acronyms, and Abbreviations.....................................................................................................4

1.4 References.......................................................................................................................................................4

1.5 Overview.........................................................................................................................................................5

2. Project Overview...................................................................................................................................................5

2.1 Project Purpose, Scope, and Objectives.........................................................................................................5

2.2 Assumptions and Constraints..........................................................................................................................6

2.3 Project Deliverables.......................................................................................................................................6

2.4 Evolution of the Software Development Plan.................................................................................................7

3. Project Organization............................................................................................................................................7

3.1 Organizational Structure................................................................................................................................7

3.2 External Interfaces..........................................................................................................................................7

3.3 Roles and Responsibilities..............................................................................................................................8

4. Management Process............................................................................................................................................8

4.1 Project Estimates............................................................................................................................................8

4.2 Project Plan....................................................................................................................................................94.2.1 Phase Plan...............................................................................................................................................94.2.2 Iteration Objectives...............................................................................................................................104.2.3 Releases.................................................................................................................................................114.2.4 Project Schedule....................................................................................................................................114.2.5 Project Resourcing................................................................................................................................12

4.3 Project Monitoring and Control...................................................................................................................13

4.3.1 Requirements Management Plan..............................................................................................................134.3.2 Schedule Control Plan...........................................................................................................................134.3.3 Budget Control Plan..............................................................................................................................134.3.4 Quality Control Plan.............................................................................................................................134.3.5 Reporting Plan......................................................................................................................................134.3.6 Measurement Plan.................................................................................................................................13

4.4 Risk Management Plan.................................................................................................................................13

4.5 Close-out Plan..............................................................................................................................................13

5. Annexes................................................................................................................................................................14



Software Development Plan (Small Project)

1. IntroductionThe Software Development Plan describes the development activities of the project. It provides detailed information about different phases and iterations and tasks required to be completed in order to accomplish the project. It also shows how long a particular phase or a task is going to take and various deliverables and milestones of the project.

1.1 Purpose

The purpose of the Software Development Plan is to gather all information necessary to control the project. It describes the approach to the development of the software and is used by the project team to schedule the development process of the project.

1.2 Scope

This document consists of the overall plan to be used for developing a bar-coded online assessment management system for Coventry University. The details of the individual iterations are described in the iteration plan document of this project. The plan described in this document is based upon the software requirements and the vision document for the project.

1.3 Definitions, Acronyms, and Abbreviations

BASIL - Bar-coded Assessment System for Independent Learning. (BASIL)RUP - Rational Unified Process

1.4 References

The list of documents referenced in this software development plan is:

Title Author YearBASIL Vision Document Yavuz Erdem 2010

BASIL User Interface Prototype Document V1.0

Ndumayak Onomo 2010

BASIL Iteration Assessment Document V1.0

Saqib Abbas 2010

BASIL Master Test Plan Document V1.0

Ndumayak Onomo 2010

BASIL Next Iteration Plan Document V1.0

Yavuz Erdem 2010

BASIL Risk Management Plan+ Risk List Document V1.0

Yavuz Erdem &Saud Aljaloud

2010

BASIL Use Case Model + SurveyVersion 1.1

Saqib Abbas 2010

Software Project Management Walker Royce 1998



1.5 Overview

The rest of the Software Development Plan document is divided into several sections which are further divided into sub-sections. Major sections of this document are:

Project Overview: This section describes the purpose, scope and objectives of this project. It also lists the deliverables of the project.

Project Organisation: This section describes the project organization and roles and responsibilities of the people involved in the project.

Management Process – This section explains the estimation of cost and effort required to do this project. It also provides the iteration objectives, major milestones and schedule of the project.

2. Project Overview

2.1 Project Purpose, Scope, and Objectives

The purpose of Bar-coded Assessment System for Independent Learning is to develop an online system that will manage Coventry University assessments. The system will use barcode technology to keep track of all assessments (both paper and electronic based) for the benefit of staff and students of Coventry University. System will have lecturer and student specific functions which will allow them to use the system according to their needs.

The project deliverables include:

Software Development Plan: is document which establishes a standardized and coherent methodology for the development activities of the BASIL.

Iteration Assessment: is used to assess and evaluate whether the Iteration Plan for a particular iteration went according to the plan.

Review Records: are the records of the meetings which take place between various stakeholders throughout the project.

Next Iteration Plan: involves laying out the plan for a particular iteration of the phase. Risk Management Plan: involves determining the maximum acceptable level of overall risk and

developing a strategy to overcome them. Vision Document: describes the overall vision and aim of the project. Supplementary Specifications: consists of non-functional requirements of the project. Use Case Model: consists of diagrammatical representation of users and the functions they will

carry out using BASIL system. Master Test Plan: contains a detailed plan of how the testing of the software will be carried out. It

describes how testing will proceed, who will be doing the testing, and what will be tested, how long will the testing take place for and to what quality level the test will be performed.

User Interface Prototype: is a detailed structure of the interfaces and their relationship between the user and the system.

Besides above deliverables, there are many other deliverables listed in the screenshot in section 4.2.4 [Project Schedule] of this document.



2.2 Assumptions and Constraints

The following assumptions will be considered during the project plan; The system must use a barcode technology to keep track of all assessments. The online system must be able to manage assessments. The project is expected to pass through four phases which are: Inception, Elaboration,

Construction and Transition. The major resources needed to execute the project include software developers, business analyst,

software tester, software/interface designer, and project manager. The system must ensure that students and staff can be able to access the online system. The cost of the implementation of BASIL is budgeted at £70,000. Project should be complete within the agreeable timescale. BASIL system should ideally have a dedicated application and database server to perform at an

optimum level.

2.3 Project Deliverables

The table below provides a list of artifacts which will be created during the course of this project. Some of the artifacts will be created more than once for different iterations of the project. The target date of artifacts for various iterations is shown the Project Schedule Gantt chart in section 4.2.4 of this document.

Artifacts Description

Software Development Plan It is a document which establishes a standardized and coherent methodology for the development activities of the project.

Iteration Assessment It is used to assess and evaluate whether the Iteration Plan for a particular iteration went according to the plan.

Review Records These are the records of the meetings which take place between various stakeholders throughout the project.

Next Iteration Plan This artifact lays out the plan for a particular iteration of the phase.

Risk Management Plan + Risk List This artifact involves determining the maximum acceptable level of overall risk and developing a strategy to overcome them.

Vision Document This artifact describes the overall vision and aim of the project.

Supplementary Specifications This artifact lists the non-functional requirements of the project.

Mater Test Plan It consists of the test phases life cycle and it’s efficiency in BASIL.

User Interface Prototype It consists of diagrams and structures which interpret the way users interact with the system in BASIL.

Use Case Model + Survey It consists of diagrammatical representation of users and the functions they will carry out using BASIL system.



2.4 Evolution of the Software Development Plan

The software development plan for the BASIL System will be updated as the project goes through different phases. It is expected to be updated at the start of all the iterations until the end of Elaboration phase of the project. The different versions of software development plan we will have during the project are listed in the below table.

Version Iteration Phases1.0 Inception – Iteration 11.1 Inception – Iteration 11.2 Elaboration - Iteration 11.3 Elaboration - Iteration 2

3. Project Organization

3.1 Organizational Structure

Organisational Structure of the Project Team of NYSS Software Solutions

3.2 External Interfaces

The NYSS Software Solutions project team will liaise with Coventry University’s IT Department, BASIL Management Team and Student Representative in order to accomplish the project. BASIL Management team will oversee the project on behalf of Coventry University while as Coventry University’s IT Department will provide information and assistance with regards to the IT Infrastructure available within the university. Project team will also liaise with Coventry University Student representative in order to gather the requirements for the BASIL system. The internal contacts of the NYSS software solutions will be the current group leader – Saqib Abbas.


Project Manager

Business Analyst Designer Developer

Tester Implementation Manager

Developer


3.3 Roles and Responsibilities

The roles and responsibilities of the various stakeholders of the BASIL project are:

ROLES RESPONSIBILITIES

Coventry University Provide finance for the project.

BASIL Management Team Liaise with Coventry University for finance. Liaise with students and lecturers to gather information

about the requirements of the system. Liaise with NYSS Software Solutions to ensure project

meets the required specification.

NYSS Software Solutions Liaise with all the stakeholders Hold regular meetings with BASIL management. Develop BASIL System

Student Representative Help with gathering requirements of the system Ensure the system meets students’ requirements.

.

4. Management Process

4.1 Project Estimates

BASIL project has been identified as a small to medium sized project and is expected to be completed within 25 weeks of the commencement of the project. 2 weeks have been earmarked for contingency. The cost of the project has been estimated at £70,000. The cost and the time required to complete this project has been worked out after making rough calculations using COCOMO 81 estimation technique. The project is classed as ‘Organic’ as project consists of a small team who will be working with familiar environment and well understood applications. The EAF (Effort Adjustment Factor) has been kept nominal when calculating effort required for the project while as the SLOC (Source Lines of Code) has been estimated to be around 200. As project is still in its infancy, the cost and schedule is liable to change until it has been agreed by both parties.

After agreeing on cost and schedule, some of the circumstances where re-estimates of schedule and cost will occur include:

Change in external requirements. Change in implementation date. Change in interface design after initial approval.

Detailed project schedule can be seen in section 4.2.4 [Project Schedule] of this document.



4.2 Project Plan

4.2.1 Phase Plan

Phase Total Number of Iterations Start End (Inclusive)Inception 1

Iteration 1 Week 1 Week 4

Elaboration 2



Construction 3




Transition 1


Milestones:

Phase Milestone

Inception Establish business case Complete requirements analysis Develop major use-cases and use-case model Develop user interface prototype

Elaboration Architecture design complete

Construction Alpha release Final use-case model complete Beta release Testing complete Software Development complete

Transition Final software release Software implemented

Gantt chart showing the allocation of time to the project phases and iterations:



(Separate Microsoft Project file for this Gantt chart is included on CD)File name is BASIL_Phases_&_Iterations_Gantt_Chart.mpp)

Information regarding release points and demos is provided in section 4.2.3 [Releases] of this document.

4.2.2 Iteration Objectives

Phase/Iteration Objectives

Inception – Iteration 1 Identify functional and non-functional requirements.Identify major risks and devise risk management plan.Identify major actors.Agree on estimated cost and schedule.Design user interface prototype.Produce iteration artifacts

Elaboration – Iteration 1 Requirements Analysis complete.Architectural prototypeSupplementary Specifications complete.Produce iteration artifacts

Elaboration – Iteration 2 All actors and use-cases identified.User interface design complete.Produce iteration artifacts

Construction – Iteration 1 Release Alpha version.Test software and fix defects.Produce iteration artifacts

Construction – Iteration 2 Release Beta version.Test software and fix bugs.Produce iteration artifacts

Construction – Iteration 3 Software development complete.Final version ready for release.Produce iteration artifacts

Transition – Iteration 1 Software released and implemented.Produce iteration artifacts



4.2.3 Releases

There will be total of 3 releases of the software namely Alpha, Beta and Final release.

Alpha release will be a demo release which will contain most of the functionality and will be evaluated by development team. After ironing out all the deficiencies captured in Alpha testing, Beta version of the software will be released. Even though Beta version will still be a demo version, it will have more functionality and more robustness than Alpha version. It will more or less resemble the final version. After further testing and ironing out of all the deficiencies within Beta version, final version of the software will then be released to the customer.

4.2.4 Project Schedule

Below screenshot of the Gantt chart shows the project schedule, dates of completion of different phases and iterations, release points, deliverables and milestones.It also shows linkage between different tasks of the project and resources required for various tasks.

Separate Microsoft Project file for this Gantt chart is included on CD. File name is BASIL_Project _Schedule_Gantt_Chart.mpp)



4.2.5 Project Resourcing

Following staff has been identified as the requirement for the accomplishment of the project.

Staff Number Experience Major Skills

Project Manager 1 A project manager should have 10 years experience in managing medium sized IT projects.

High quality project management skills, PRINCE 2 qualified, excellent interpersonal skills, RUP knowledge.

Business Analyst 1 Business Analyst should have 5-7 years experience in business analysis of small to medium sized IT projects.

Business Analysis, requirements analysis techniques, ability to translate user requirements into technical specification.

Software/Interface Designer

1 Software/Interface Designer should have 5 years experience in designing software and interface for IT systems. Designer should have a good design portfolio.

Advanced knowledge of HCI principles, ability to use software design packages to an advanced level.

Software Developer

2 Each software developer should have an experience of about 6 years in developing medium sized IT systems.

Advanced knowledge of 2-3 programming languages and ability to convert requirements specification into an executable code and working system.

Software Tester 1 5 years experience in testing software systems.

Ability to devise test plan for the system, assess test plan results and relay them to software developers. Ability to create test scripts for the system.

Implementation Manager

1 5 years experience in software implementation of medium sized IT projects.

Ability to devise an integration plan for the project team and the customer. Good understanding and practical experience of integrating various systems.



Specialist IT recruitment consultancy will be contacted in order to acquire the required staff to accomplish the project. Project team members will not be expected to undergo any special training to accomplish the project as only experienced staff will be hired for the project.

4.3 Project Monitoring and Control

4.3.1 Requirements Management Plan

The requirement management plan for the BASIL system is referenced in the vision document authored by Yavuz Erdem, and also in the Supplementary Specification document authored by Saud Aljaloud respectively.

4.3.2 Schedule Control Plan

In this given project it is the duty of the project manager to oversee all the flaws and changes in the development of the project. This may be because one department or the other are not giving the expected deliverables, or they are running behind schedule. This section is mainly to assemble all the teams together, and if there is any change in requirements in order to maintain control of the changes and to correct any errors in order to enhance the performance of the BASIL system.

4.3.3 Budget Control Plan

This monitors funding, so that costing or spending will not be higher than the estimated project budget. Accurate costs are allocated to various teams in each of the iteration phase and the teams work strictly on the given amount or budget so that the BASIL system will not run into a “BUDGET DEFICIT”.

4.3.4 Quality Control Plan

The quality control plan that will be initiated in this project is knowing the system requirements, it’s principles, methods, and the required quality tools that are to be used and implementing changes if the need arises in the BASIL system.

4.3.5 Reporting Plan

This involves coordination between the team members to accomplish goals, monitoring projects and evaluating the outcomes of each phase, which is done on a weekly basis

4.3.6 Measurement Plan

The measurement plan for the BASIL system is referenced in the Iteration Assessment document authored by Saqib Abbas

4.4 Risk Management Plan

The risk management plan for the BASIL system is referenced in the Risk Management Plan + Risk List document authored by Yavuz Erdem and Saud Aljaloud.

4.5 Close-out Plan

The close- out plan for the BASIL system will ensure that the schedules, budgets, feasibility, risk assessment, requirements, progress and compatibility of the system are all resolved and the project is ready to be released to the stakeholders for it to be usable.

5. AnnexesThis project will follow the RUP for Small Projects process.
