University Of Oslo
Faculty of Mathematics and Natural Sciences
Department of Informatics
Sales and Customer
Tracking System
(Scats)
Project Group: 22
Version: Draft
Authors:
Belete Ayele Asfaw
beletea@ifi.uio.no
Mihail Korabelnikov
mihailk@ifi.uio.no
Juma Hermed Lungo
jumal@ifi.uio.no
Miria Grisot
miriag@ifi.uio.no
Jose L. Nhampossa
leopoldo@ifi.uio.no
Ou Weiqing
ouw@ifi.uio.no
Johnny Nordvik
johnnyno@ifi.uio.no
05, October 2001
SOFTWARE DEVELOPMENT PLAN
CONTENTS
1.
INTRODUCTION.....................................................................................................2
1.1
1.2
1.3
1.4
PROJECT OVERVIEW................................................................................................2
PROJECT DELIVERABLES .........................................................................................2
EVOLUTION OF THE SOFTWARE PROJECT MANAGEMENT PLAN............................2
REFERENCE MATERIALS ..........................................................................................3
2.
PROJECT ORGANIZATION ...................................................................................4
2.1
2.4
PROCESS MODEL .....................................................................................................4
PROJECT RESPONSIBILITIES ..................................................................................4
3.
MANAGERIAL PROCESS .......................................................................................6
3.1
3.2
3.3
3.4
3.5
MANAGEMENT OBJECTIVES AND PRIORITIES ........................................................6
ASSUMPTIONS, DEPENDENCIES, AND CONSTRAINTS ..........................................6
RISK MANAGEMENT ................................................................................................6
MONITORING AND CONTROLLING MECHANISMS ..................................................6
STAFFING PLAN .......................................................................................................6
4.
TECHNICAL PROCESS...........................................................................................7
4.1
4.2
4.3
METHODS, TOOLS, AND TECHNIQUES ..................................................................7
SOFTWARE DOCUMENTATION.................................................................................7
PROJECT SUPPORT FUNCTIONS..............................................................................7
5.
WORK BREAKDOWN AND SCHEDULE ...............................................................8
6.
ADDITIONAL COMPONENTS .............................................................................10
7.
INDEX ...................................................................................................................11
8.
APPENDICES ........................................................................................................12
106753542 (03/08/16)
Page 1
SOFTWARE DEVELOPMENT PLAN
1.
INTRODUCTION
1.1 Project Overview
The project aim is to develop a computer application to support the BOC
organization on office equipment sell. A complex PC spreadsheet is being
actually used to track and forecast customer buying patterns, thus: Slow to
catch buying trend, prone to errors and overwhelming (crashes).
The application is expected to open new markets and increase sales
opportunities, to handle more customers, to increase flexibility and speed of
activity and improve the management and planning.
1.2 Project Deliverables
The following items are to be delivered to the customer:

The project plan

System requirements

SCATS

Customer Training

User manual documentation
1.3 Evolution of the Software Project Management
Plan
Version
Primary
Author(s)
Description of Version
Date
Expected
Draft
José Leopoldo
Nhampossa
Initial draft created for distribution
and review comments
051001
Preliminary
TBD
Second draft incorporating initial
review comments, distributed for
final review
TBD
Final
TBD
First complete draft, which is
placed under change control
TBD
Revision 1
TBD
Revised draft, revised according to
the change control process and
maintained under change control
TBD
106753542 (03/08/16)
Page 2
SOFTWARE DEVELOPMENT PLAN
Version
Primary
Author(s)
Description of Version
Date
Expected
etc.
TBD
TBD
TBD
1.4 Reference Materials
1. I Sommerville, Software Engineering, 6th edition, Addison-Wesley,
2001.
2. J. Cadle, D. Yeates, Project Management for Information Systems, 3th
edition, Prentice hall, 2001.
3. User Requirements documentation.
106753542 (03/08/16)
Page 3
SOFTWARE DEVELOPMENT PLAN
2.
PROJECT ORGANIZATION
2.1 Process Model
The incremental process model will be fellowed for the development of the
present project.This model is based on the principle that the total
functionality of the system, meaning the introduction of the new system to
the organization, can be delivered in phases over a period of time. This
implies that, compared with other models, delivery and testing are more
manageable since they allow familiarization with changes and allow as well
having experience with the system before more detailed requirements have
to be decided. In this way customers gain value from the system without
waiting until the whole system is ready.
Once an increment is completed, the customers can experiment with the
system and in this way clarify requirements for later increments. This lowers
the risk of failure.
It is important that the total scope of the definition of requirements is
completed before the increments are defined. It develops as follows:
1. The customer identifies the services specifying which have to be
prioritised and which are less important. The definition of the
increments is done allocating the services according to their priority:
the highest are delivered in the early increments.
2. The definition of critical requirements for the first increment has to be
completed in detail, and then the increment is developed. During the
development requirements cannot be changed.
3. As the increment is completed and delivered, it can be put it into
service.
4. Increments are integrated with existing ones as they are completed.
2.4 Project Responsibilities
Responsibility
Persons responsible
Overall Project Manager
José Leopoldo Nhampossa
Programmer
Weiqing, Ou
Quality Assurance Manager
Miria Grisot
End-User Documentation Manager
Johnny Nordvik
Web Master
Lungo, Juma Hemed
106753542 (03/08/16)
Page 4
SOFTWARE DEVELOPMENT PLAN
Responsibility
Persons responsible
Software Engineer
Korabelnikov, Mihail
Software Engineer
Asfaw, Belete Ayele
106753542 (03/08/16)
Page 5
SOFTWARE DEVELOPMENT PLAN
3.
MANAGERIAL PROCESS
3.1 Management Objectives and Priorities
(TBD)
3.2 Assumptions, Dependencies, and Constraints
(TBD)
3.3 Risk Management
(TBD)
3.4 Monitoring and Controlling Mechanisms
(TBD)
3.5 Staffing Plan
(TBD)
106753542 (03/08/16)
Page 6
SOFTWARE DEVELOPMENT PLAN
4.
TECHNICAL PROCESS
4.1 Methods, Tools, and Techniques





The system will be developed on a UNIX based platform on SUN
SPARCstation.
A CASE tool named Tau_UML will be used in the development process. All
documentation will be processed trough Microsoft Word.
The application will be coded in Java and the code conventions for the
Java programming language will be followed.
The quality assurance practices will be updated in the final version of the
project plan.
A test plan will be developed for the execution and tracking of test
activities. This plan will be finished as soon as the System Specification
Requirements document is in final version.
4.2 Software Documentation
The System Requirement Document and other documents generated in a
later stage of the project will be placed under explicit version control after the
final version is made. The built in Version Control of Word will be used for this
purpose.
The Tau_UML suite will be used for modeling the SCATS application. The built
in version control in Tau_UML will be used to secure the version control of the
modeling.
Documentation of the SCATS application will be delivered as comments in
the JAVA code.
4.3 Project Support Functions
A plan for Configuration Management and a plan for Quality Assurance will be
developed as soon as the final version of the System Requirement
Specification is valid.
106753542 (03/08/16)
Page 7
SOFTWARE DEVELOPMENT PLAN
5.
WORK BREAKDOWN AND SCHEDULE
In this part we describe the breakdown of the project into activities and
identifies the milestone and deliverables associated with each activities.
1. Requirements analysis
The requirements submitted by the customer group should be
analysed and a requirements specification report will be produced
as a project deliverable.
2. Hardware and Software Installation
Hardware and Software will be determined and this task will be
accomplished by delivering hardware and software specifications
(development platform).
3. Database Design
The database of the system shall be designed. The milestone will be
Database design report.
4. User interface design
User interface should be design and a report for user interface
design will be delivered.
5. Interface Design
This specifies how the application program will connect to the
database system. An interface design report shall be given as a
milestone. The deliverable for the three activities (Database design,
User interface design and Interface design) will be the software
design specifications.
6. Database Implementation
Depending the Relational Database System specified in the design
phase, the database tables and relationships would be
implemented. Documentation for the database tables and table
relationship shall be given.
7. Software Implementation
The actual programming will be carried out. CASE tools may be
used generate a skeleton program from the design. The deliverable
here will be a working system.
106753542 (03/08/16)
Page 8
SOFTWARE DEVELOPMENT PLAN
8. System Testing
The system will be tested in the presence of our customer. A
system testing report will be delivered as a milestone
9. System Manual
This activity will involve writing down the User’s Guide Manual
10. System delivery and User training
The activity will include delivering the system to the customer by
installing the system to their office and give training on how to use
the system
TASK DURATIONS AND DEPENDENCIES
TID
TASK
DURATION
T1
Requirement Analysis and Specification
(M1)
3
T2
Hardware and Software Installation
2
T3
Database
(M2)
Design
3
T1 (M1)
T4
User
(M3)
Design
4
T1 (M1)
T5
Interface Design
2
T3 (M2)
T6
Database
(M4)
Implementation
3
T3
T7
Software
(M5)
Implementation
20
T8
System Testing
T9
Develop
(M6)
Interface
User’s
Manual
T10 System delivery and User Training
106753542 (03/08/16)
DEPENDENCIES
T4, T5
4
T7 (M5)
6
T7 (M5)
3
T7 , T)
Page 9
SOFTWARE DEVELOPMENT PLAN
6.
ADDITIONAL COMPONENTS
(TBD)
106753542 (03/08/16)
Page 10
SOFTWARE DEVELOPMENT PLAN
7.
INDEX
(TBD)
106753542 (03/08/16)
Page 11
SOFTWARE DEVELOPMENT PLAN
8.
APPENDICES
(TBD)
106753542 (03/08/16)
Page 12