SRS for Bank Proj
-
Upload
alaa-arori -
Category
Documents
-
view
2.778 -
download
8
Transcript of SRS for Bank Proj
Bank Operations Project
System Project Management Plan
Version: SPMP 1.1
Prepared by
Team #20
Sheldox Team
Mazhar Isık– Cagri Diken – Mehmet Kocak
October 21th, 2009
BANK OPERATIONS
Preface
This project plan document is designed for
Supervisor – to control team members and their works which is suitable for the
protection or not.
Customer – to explain a project detail and wants something about the project.
Team members – choose the best solution and complete the expected
product.
It covers a summary about the project that includes purpose, scope and objectives,
assumptions and constraints of the project. Deliverables are identified. Add them up,
schedule and budget summary is identified.
Assigning roles and responsibilities to team members are defined in this report. Software
Project Managerial process plans are applied for the estimation, stuffing, resource
allocation, quality control and risk management.
Atılım University
COMPE 491-492
2/41
Team # 20 (Team Sheldox)
System Project Management Plan
Version: 1.0
BANK OPERATIONS
Version History
Version Status* Date Responsible Version Definition
1 Released 22.08.2009 Cagri Diken, Sadık Mazhar Isık, Mehmet Kocak
Baseline Version of SPMP
2 In Change 22.11.2009 ……. ……
*: Draft, In Review, Released, Approved, Rejected, In Change
Atılım University
COMPE 491-492
3/41
Team # 20 (Team Sheldox)
System Project Management Plan
Version: 1.0
BANK OPERATIONS
List of Tables
Table 1: Product Function I/O Summary
Table 2: Function Point Metrics
Table 3: Complex Adjustment Values
Table 4: Project Work Activity
Table 5: Resource Allocation for Work Activity
Table 6: Resource Allocation for Customer Meeting
Table 7: Resource Allocation for Preparing SPMP
Table 8: Resource Allocation for Preparing SRS
Table 9: Resource Allocation for Preparing SDD
Table 10: Resource Allocation for Preparing STD
Table 11: Resource Allocation for Coding
Table 12: Resource Allocation for Testing
Table 13: Resource Allocation for Preparing User Manual
Table 14: Resource Allocation for Deployment
Table 15: Schedule and Budget Allocation for Customer Meeting
Table 16: Schedule and Budget Allocation for Preparing SPMP
Table 17: Schedule and Budget Allocation for Preparing SRS
Table 18: Schedule and Budget Allocation for Preparing SDD
Table 19: Schedule and Budget Allocation for Preparing STD
Atılım University
COMPE 491-492
4/41
Team # 20 (Team Sheldox)
System Project Management Plan
Version: 1.0
BANK OPERATIONS
Table 20: Schedule and Budget Allocation for Coding
Table 21: Schedule and Budget Allocation for Testing
Table 22: Schedule and Budget Allocation for User Manuel
Table 23: Schedule and Budget Allocation for Deployment
Atılım University
COMPE 491-492
5/41
Team # 20 (Team Sheldox)
System Project Management Plan
Version: 1.0
BANK OPERATIONS
Table of Contents
PREFACE............................................................................................................................2
LIST OF TABLES................................................................................................................4
TABLE OF CONTENTS.......................................................................................................6
1. OVERVIEW................................................................................................................8
1.1. Project Summary.....................................................................................................81.1.1. Purpose, Scope, and Objectives......................................................................81.1.2. Assumptions and Constraints...........................................................................81.1.3. Project Deliverables..........................................................................................91.1.4. Schedule and Budget Summary.....................................................................10
1.2. Evolution of the SPMP..........................................................................................10
2. REFERENCE MATERIALS.....................................................................................12
3. DEFINITIONS, ACRONYMS, AND ABBREVIATIONS...........................................13
4. PROJECT ORGANIZATION....................................................................................14
4.1. External Interfaces................................................................................................144.2. Internal Structure...................................................................................................144.3. Project Responsibilities.........................................................................................14
5. MANAGERIAL PROCESS PLANS.........................................................................16
5.1. Start-up Plan.........................................................................................................165.1.1. Estimation Plan...............................................................................................165.1.2. Resource Acquisition Plan..............................................................................205.1.3. Project Staff Training Plan..............................................................................20
5.2. Work Plan..............................................................................................................205.2.1. Work Activities................................................................................................205.2.2. Schedule Allocation........................................................................................235.2.3. Resource Allocation........................................................................................245.2.4. Budget Allocation............................................................................................29
5.3. Control Plan..........................................................................................................345.3.1. Requirements Control Plan............................................................................345.3.2. Schedule Control Plan....................................................................................345.3.3. Quality Control Plan........................................................................................345.3.4. Reporting Plan................................................................................................355.3.5. Metrics Collection Plan...................................................................................35
5.4. Risk Management Plan.........................................................................................35
6. TECHNICAL PROCESS PLANS.............................................................................38
6.1. Process Model......................................................................................................386.2. Methods, Tools, and Techniques..........................................................................386.3. Infrastructure Plan.................................................................................................386.4. Product Acceptance Plan......................................................................................39
7. TECHNİCAL PROCESS PLANS.............................................................................40
7.1. Configuration Management Plan...........................................................................407.2. Quality Assurance Plan.........................................................................................407.3. Documentation Plan..............................................................................................40
Atılım University
COMPE 491-492
6/41
Team # 20 (Team Sheldox)
System Project Management Plan
Version: 1.0
BANK OPERATIONS
7.4. Deployment Plan...................................................................................................407.5. Review Plan..........................................................................................................40
Appendices.........................................................................................................................41
Atılım University
COMPE 491-492
7/41
Team # 20 (Team Sheldox)
System Project Management Plan
Version: 1.0
BANK OPERATIONS
1. Overview
1.1. Project Summary
1.1.1. Purpose, Scope, and Objectives
1.1.1.1 PurposeThe aim of our senior project which is Bank Operations is to design and develop a
software and network system. It provides easy communication between center and
all of the bank agency offices.
1.1.2 Scope
The scope of our project is serving fast service for the bank customers. Add them
up, fast connection between center and all bank offices. If a problem occurs in the
system, all of the bank agency offices will not be affected, because every 5
minutes the system takes backup automatically.
In addition, our network connected from center to the bank agency offices. We
create a special line for this bank system.
As a result, customer takes faster services, and bank employees making
operations in easy user interface.
1.1.2.1 Objectives
When project will finish, our system will be capable of followings;
Bank operator’s will use easily due to visual program.
System can not be interrupt due to the special network.
All of the money currencies are seeing by the user, on the user interface.
All of the bank operations can make from the bank operator’s screen.
The program has a login page, so only authorized people enter the system.
Atılım University
COMPE 491-492
8/41
Team # 20 (Team Sheldox)
System Project Management Plan
Version: 1.0
BANK OPERATIONS
1.1.2. Assumptions and Constraints
1.1.2.1 Assumptions
We assumed that the following points exist.
All users are familiar to Windows Applications.
All users should have background of bank operations.
All team members of project will know the bank operations so
they are searching bank operations.
All team members will realize their responsibilities.
All team members should apply the SPMP process rules
1.1.2.2 Constraints
The system constraints are
The program will work on the machines which have Windows
Xp/Vista.
Adobe flash player should be installed in users computer.
Developers are expected to obey all the schedule restrictions.
1.1.3. Project Deliverables
There are four major deliverables in the project which are SPMP, SRS,
SDD, and STD. All these documents will be prepared according to the
IEEE standards.
All of the deliverables are downloaded from the project website. If there are
any changes or updates, it will be announcement from us.
SPMP (Software Project Management Plans): It defines all of the
information about the project and team members. This information are
created by assumptions. During the project lifecycle in formations may be
change, and specify roles and responsibilities of team members. It must be
document the deliverables and their deadlines
SRS (Software Requirements Specification): It defines the requirements of
software. Software has two kinds of requirements which are functional and
Atılım University
COMPE 491-492
9/41
Team # 20 (Team Sheldox)
System Project Management Plan
Version: 1.0
BANK OPERATIONS
non-functional. It documents all of this requirements and includes a set of
use cases which describes the user-system interactions.
SDD (Software Design Description): It defines the description of design of
the software. It must be included all of the information about design and
document it.
STD (Software Test Documentation): It defines the test plans of software.
STD includes verification and validation activity and their results. All in
formations are document such as test cases, test procedures, test plan …
etc.
1.1.4. Schedule and Budget Summary
1.1.4.1 Schedule
Our project schedule becomes two points.
1- Constant deliverables times which is announced by supervisor.
2- Team members’ weekly schedule.
This is the initial version of the first deliverable of the project, and we
don’t have enough experience to predict time. In later versions, time will
estimated to each task of project.
1.1.4.2 Budget
For estimating budget we use function point, and Cocomo model. You can
check our calculation in the table which exists in the estimation plan section.
1.2. Evolution of the SPMP
SPMP will all changes to the project management plan must be agreed to by group
members before they are implemented. . All changes should be documented in
order to keep the project management plan correct and up to date. This report is
the initial version, so it likes to initial plan. In future, there will be other deliverables
such as SRS, SDD, STD. After deciding use cases and preparing SRS, our project
Atılım University
COMPE 491-492
10/41
Team # 20 (Team Sheldox)
System Project Management Plan
Version: 1.0
BANK OPERATIONS
develops clearly. In future our project can change by customer wants or using
platforms. For this reason, there will be some changes on SPMP. As a result,
SPMP has lots of version. In each version we make changes and updates. Finally,
the last version of SPMP will show the corrects about projects.
Atılım University
COMPE 491-492
11/41
Team # 20 (Team Sheldox)
System Project Management Plan
Version: 1.0
BANK OPERATIONS
2. Reference Materials
IEEE Std 1058-1998, IEEE Standard for Software Project Management Plans
Pressman, Roger S., Software Engineering, 4th edition, McGraw-Hill, 1997
Fairley, R. E., Workbreakdown Structure, Software Engineering Project Management, IEEE CS Press, 1997
Software Project Management, Bob Hughes&Mike Cotterell, McGraw-Hill Publication, 2006.
http://www.atilim.edu.tr/~aakca/2009/491_492/refs/SPMP_v1.1.doc
http://www.bilmuh.gyte.edu.tr/BIL441/studentfiles/ch7%20-%20Kopya_tr.ppt#14
http://pdfdatabase.com/download_file_i.php?file=10819252&desc=Level+1+Engineering+Requirements+.pdf
Atılım University
COMPE 491-492
12/41
Team # 20 (Team Sheldox)
System Project Management Plan
Version: 1.0
BANK OPERATIONS
3. Definitions, Acronyms, and Abbreviations
SMPM: Software Project Management Plan
SRS: Software Requirements Specifications
HW: Hardware
SW: Software
B.O: Bank operations
GUI: Graphical user interface
Ns: Network System
DBM: Database Management
DB: Database
DBMS: Database Management System
PM: Project Management
A.S: Application Server
FW: Firewall
IEEE: Institute of Electrical and Electronics Engineers
HTML: Hypertext Markup Language
COCOMO: Constructive Cost Model
WBS: Work Breakdown Structure
SRE: Software Requirement Engineering
SPM: Software Project Management
Atılım University
COMPE 491-492
13/41
Team # 20 (Team Sheldox)
System Project Management Plan
Version: 1.0
BANK OPERATIONS
4. Project Organization
4.1. External Interfaces
Our main customer is KBC Bank. We arrange a meeting with Levent FEREN who
is in the KBC Bank. The meeting will held twice in a month. All team members
expected to come those meetings. After the meeting we will talk with project
supervisor and we will discuss some points.
4.2. Internal Structure
We are two people who work for this project, so we have only management and
development structures. Each member of team should manage themselves and has to
control the other and also both of us in development team which should work parallel,
fast and productive.
4.3. Project Responsibilities
We indentify the roles and defined below. Add them up, all of the group members
are responsible for every phase in the project life cycle.
Mazhar Isık;
Project Manager
Configuration Manager
Developer
Tester
Cagri Diken;
Web Designer
Configuration Manager
Developer
Tester
Mehmet Kocak;
Database Designer
Atılım University
COMPE 491-492
14/41
Team # 20 (Team Sheldox)
System Project Management Plan
Version: 1.0
BANK OPERATIONS
Network Developer
Developer
Tester
Project Manager: Manage all parts of the project, coordinates the team.
Configuration Manager: Manage the documents.
Web Designer: Deals with the web aspect of the project
Developer: Responsible for every development activities.
Tester: Check the systems if there is a mistake or not.
Database Designer: Responsible for entire database system.
Network Developer: Responsible for network system.
Atılım University
COMPE 491-492
15/41
Team # 20 (Team Sheldox)
System Project Management Plan
Version: 1.0
BANK OPERATIONS
5. Managerial Process Plans
5.1. Start-up Plan
This section defines our projects’ plan such as estimation, staffing,
resource acquisition, and training plan. All of them will be defined in details
from the following subsections.
5.1.1. Estimation Plan
We are not gain enough experience for making estimation before the
beginning of project, so it is too hard to estimate. This is the first version of
SPMP and we have not got sufficient date and information for making
estimation. We use function point method for estimation.
Inputs Outputs Inquiries
Name
Surname
Gender
Birth Date
Maiden name
Father name
Education status
TC Identity number
Home Address
Village
Post Code
City
City Location
Telephone
GSM
Account number
Pay amount
Information
Credit Card Number
Account number
Account amount
Credit Card user limit
Account amount
# of FON
Account amount
Gaining amount
Account amount
Sender Account amount
Receiver Account amount
Money Transfer Commission
Login True/False
Account Amount/ Foreign Exchange
Account number
Opening office interface
Report Preparation
Product Size Request
Atılım University
COMPE 491-492
16/41
Team # 20 (Team Sheldox)
System Project Management Plan
Version: 1.0
BANK OPERATIONS
Pay Amount
Account Number
Withdrawn Amount
Account number
Number of FON
Account Number
Pay Amount
Compound Time in months
Name
Surname
Address
Telephone
Money transfer amount
Money type
Information
Sender Account Number
Bank Office Name
Receiver Account Amount
Name
Surname
Username
Password
Foreign Exchange Type
Pay Amount
Account Number
Name
Surname
TC Identity number
Bank Office name
Bank Office code
Table1: Product Function I/O Summary
Atılım University
COMPE 491-492
17/41
Team # 20 (Team Sheldox)
System Project Management Plan
Version: 1.0
BANK OPERATIONS
Number of inputs: 50
Number of outputs: 16
Number of inquiries: 2
Number of files: There exist no files.
Number of external interface: 2 (Oracle, Windows Server Application)
Measurement Parameter
Count(C) Weighting Factor (W) W*C
Inputs 50 4 200
Outputs 16 5 80
Inquiries 2 4 8
Files 0 10 0
External Interfaces 2 7 14
TOTAL 302
Table 2: Function Point Metrics
Influence Factor Weight
1 Backup and recovery 5
2 Data communications 5
3 Distributed processing 3
4 Performance Critical 5
5 Existing Operating Environment 4
6 On-line data entry 5
7 Input transaction over multiple screens 4
8 ILFs update online 5
Atılım University
COMPE 491-492
18/41
Team # 20 (Team Sheldox)
System Project Management Plan
Version: 1.0
BANK OPERATIONS
9 Information domain values complex 1
10 Internal processing complex 1
11 Code design for reuse 3
12 Conversion / installation in design 1
13 Multiple installations 0
14 Application Designed for change 0
Sum (Fi) 42
Table3: Complex Adjustment Values
FP = Count-Total * [0.65 +0.01*Sum(Fi)]
FP=302-42*[0.65+0.01*42]
FP=257.06
COCOMO
LOC = FP * Language Factor
We use object oriented language, which is C#, during the developing Bank
Operations System. Language factor C# is 56.
LOC=257.06*56=14395.36
KLOC=14395.36/1000=14.39536
Then we use the basic Cocomo equations. E identifies effort, and D identifies
duration.
E=ab(KLOC)bb
D=cb (E) d
b
Our project is semi-detached, so we use
Atılım University
COMPE 491-492
19/41
Team # 20 (Team Sheldox)
System Project Management Plan
Version: 1.0
BANK OPERATIONS
ab = 3,0 ; 1,12 bb=1,12 ; 2,5 cb=2,5 and for d
b=0,35
E=3,0*(14.39536)1,12 =59.474457 person-month
D=2,5*(59.474457)0,35=10.44 months
E/D ratio gives the recommended number of people.
E/D=59.474457/10.44=5.706366≈~6 (approximately)
As our group consist of 3 people, so we are not fulfill necessary human resources,
so we must increase our performance, and work more.
5.1.2. Resource Acquisition Plan
During the project we will use personal Computers. We will examine and
choose available solution alternatives and acquire. Following requirements
are enough to instantiate the program.
5.1.3. Project Staff Training Plan
Every group member will make search, revise their knowledge by using book, lecture
notes, internet ... etc in their free times. Every member of the team is responsible for each
phase in the project, so we must spare a suitable time. Our team members meet 3 or 4
day of every week. It depends on our exam schedule. The team will spend one day only
for meeting. The members make conversation and during the meeting new things will be
created, other days are workshops. On the other hand each member works individual in
his free time.
5.2. Work Plan
5.2.1. Work Activities
1.0 CUSTOMER MEETING
1.1 Contact with customer
1.2 Problem Description
1.3 Requirements Gathering
Atılım University
COMPE 491-492
20/41
Team # 20 (Team Sheldox)
System Project Management Plan
Version: 1.0
BANK OPERATIONS
2.0 PREPARING SPMP
2.1 Work Products & Activities Decomposition
2.2 Product Size Estimation
2.3 Process Model
2.4 Resource Allocation
2.5 Schedule Allocation
2.6 Risk Management Plan
2.7 Technical Process Plans
2.8 Supporting Process Plans
2.9 Documentation
2.10 Review of SPMP
2.11 Revised SPMP
2.12 Approval of SPMP
3.0 PREPARING SRS
3.1 Contact with Customer
3.2 Formal Identification of User Group
3.3 Product Functions
3.4 Behavioral Requirements Specification
3.5 Non-Behavioral Requirements Specification
3.6 Documentation
3.7 Review of SRS
3.8 Revised SRS
3.9 Approval of SRS
4.0 PREPARING SDD
4.1 SDD Basic Concepts
4.2 Database Design
Atılım University
COMPE 491-492
21/41
Team # 20 (Team Sheldox)
System Project Management Plan
Version: 1.0
BANK OPERATIONS
4.3 Interface Design
4.4 Algorithms Design
4.5 Network System & Security Design
4.6 Documentation
4.7 Review of SDD
4.8 Revised SDD
4.9 Approval of SDD
5.0 PREPARING STD
5.1 V&V Management
5.2 V&V Acquisition
5.3 V&V Supply
5.4 V&V Development
5.5 V&V Operation
5.6 V&V Maintenance
5.7 Documentation
5.8 Review of STD
5.9 Revised STD
5.10 Approval of STD
6.0 CODING
6.1 C#
6.1.1 C# User Interface
6.1.2 C# Windows Applications
6.2 Oracle
6.3 CODE REVIEW
6.3.1 Authorization
6.3.2 User interface design
Atılım University
COMPE 491-492
22/41
Team # 20 (Team Sheldox)
System Project Management Plan
Version: 1.0
BANK OPERATIONS
6.3.3 C# Oracle Integration
6.3.4 Report Preparation
7 TESTING
7.1 Unit Test
7.2 Integration Test
7.3 System Test
8 USER MANUAL
8.1 Preparation of User Manual
8.2 Revised User Manual
9 DEPLOYMENT
9.1 Approval of the product
Table 4: Project work activity
5.2.2. Schedule Allocation
Work activity has not any defined start and end dates, but SPMP, SRS,
SDD and STD deadlines are defined by supervisor. Product should be
introduced at he end of the first semester which is demo, and product will
produced at the end of the second semester.
Atılım University
COMPE 491-492
23/41
Team # 20 (Team Sheldox)
System Project Management Plan
Version: 1.0
BANK OPERATIONS
5.2.3. Resource Allocation
WORK ACTIVITY
REQUIRED SKILL BASED ON
Customer Meeting
Communication SkillsFace to face, E-
Preparing SPMP
Knowledge of IEEE Std and Estimation Techniques, Planning And Coordination
IEEE Std
Preparing SRS SPM, SW Engineering, SRE IEEE Std
Preparing SDD SPM,SW EngineeringIEEE Std. 1058-
1998
Preparing STD SPM,SW Engineering IEEE Std
Coding Knowledge of C#, PHP and Oracle IEEE Standards
TestingKnowledge Of Control Engineering and Testing
TechniquesIEEE Standards
User Manual Knowledge of User Manual Standard IEEE Std
Deployment Knowledge of Review Techniques IS Standards
Table 5: Resource allocation for Work Activity
CUSTOMER MEETING
WBSWORK PACKAGES SW TOOLS HUMAN RESOURCES
HW RESOURCES
1.1 Contact with customer - Team -
1.2 Problem Description Ms Office Team PC
1.3 Requirements Gathering
Ms Office,
Mozilla Firefox 3.0
Team PC
Table 6: Resource Allocation for customer Meeting
Atılım University
COMPE 491-492
24/41
Team # 20 (Team Sheldox)
System Project Management Plan
Version: 1.0
BANK OPERATIONS
PREPARING SPMP
WBS WORK PACKAGES SW TOOLS HUMAN RESOURCES
HW RESOURCES
2.1 Work Products & Activities Decomposition
MS Office, MS Project
Team PC
2.2 Product Size Estimation MS Office Team PC
2.3 Process Model MS Office Team PC
2.4 Resource Allocation MS Office Team PC
2.5 Schedule Allocation MS Office Team PC
2.6 Risk Management Plan MS Office Team PC
2.7 Technical Process Plans MS Office Team PC
2.8 Supporting Process Plans MS Office Team PC
2.9 Documentation MS Office Team PC
2.10 Review of SPMP - Supervisor and Customer
-
2.11 Revised SPMP MS Office Team PC
2.12 Approval of SPMP - - -
Table 7: Resource Allocation for preparing SPMP
PREPARING SRS
WBS WORK PACKAGES SW TOOLS
HUMAN RESOURCES
HW RESOURCES
3.1 Meeting with Customer - Team -
3.2 Product Functions Ms Office Team PC
3.3 Behavioral Requirements Specification
Ms Office Team PC
3.4 Non-Behavioral Requirements Specification
Ms Office Team PC
Atılım University
COMPE 491-492
25/41
Team # 20 (Team Sheldox)
System Project Management Plan
Version: 1.0
BANK OPERATIONS
3.5 Documentation Ms Office Team PC
3.6 Review of SRS - Supervisor and Customer
PC
3.7 Revised SRS Ms Office Team PC
3.8 Approval of SRS - - PC
Table 8: Resource Allocation for preparing SRS
PREPARING SDD
WBS WORK PACKAGES SW TOOLS
HUMAN RESOURCES
HW RESOURCES
4.1 SDD Basic Concepts - Team -
4.2 Database Design Ms Office Team PC
4.3 Interface Design Ms Office Team PC
4.4 Algorithms Design Ms Office Team PC
4.5 Network System & Security Design
Ms Office Team PC
4.6 Documentation Ms Office Team PC
4.7 Review of SDD - Supervisor and Customer
PC
4.8 Revised SDD Ms Office Team PC
4.9 Approval of SDD - - PC
Table 9: Resource Allocation for preparing SDD
PREPARING STD
WBS WORK PACKAGES
SW TOOLS HUMAN RESOURCES
HW RESOURCES
5.1 V&V Management MS Office Team PC
5.2 V&V Acquisition MS Office Team PC
Atılım University
COMPE 491-492
26/41
Team # 20 (Team Sheldox)
System Project Management Plan
Version: 1.0
BANK OPERATIONS
5.3 V&V Supply MS Office Team PC
5.4 V&V Development
MS Office Team PC
5.5 V&V Operation MS Office Team PC
5.6 V&V Maintenance MS Office Team PC
5.7 Documentation MS Office Team PC
5.8 Review of STD - - PC
5.9 Revised STD MS Office Team PC
5.10 Approval of STD - - PC
Table 10: Resource Allocation for preparing STD
CODING
WBS WORK PACKAGES
SW TOOLS HUMAN RESOURCES
HW RESOURCES
6.1C#
Visual Studio 2005
Team PC
6.1.1C# user interface
Visual Studio 2005
Team PC
6.1.2 C# Desktop Application
Visual Studio 2005
Team PC
6.2 Oracle Oracle Team PC
6.3CODE REVIEW
Visual Studio 2005
Team PC
6.3.1Authorization
Visual Studio 2005
Team PC
6.3.2User interface design
Visual Studio 2005
Team PC
6.3.3 C# & Oracle integration
Visual Studio 2005
Team PC
6.3.4 Report Preparation MS Office Team PC
Table 11: Resource Allocation for Coding
Atılım University
COMPE 491-492
27/41
Team # 20 (Team Sheldox)
System Project Management Plan
Version: 1.0
BANK OPERATIONS
TESTING
WBS WORK PACKAGES
SW TOOLS HUMAN RESOURCES
HW RESOURCES
7.1Unit Test
Visual Studio 2005
Team PC
7.2Integration Test
Visual Studio 2005
Team PC
7.3 System Test Team PC
Table 12: Resource Allocation for preparing Testing
USER MANUAL
WBS WORK PACKAGES SW TOOLS
HUMAN RESOURCES
HW RESOURCES
8.1 Preparation of User Manual
MS Office Team PC
8.2 Revised User Manual MS Office Team PC
Table 13: Resource Allocation for preparing User Manual
DEPLOYMENT
WBS WORK
PACKAGES
SW
TOOLS
HUMAN
RESOURCES
HW
RESOURCES
9.1Approval of the
Product
- Team PC
Table 14: Resource Allocation for Deployment
Atılım University
COMPE 491-492
28/41
Team # 20 (Team Sheldox)
System Project Management Plan
Version: 1.0
BANK OPERATIONS
5.2.4. Budget Allocation
Customer Meeting
WBS Work Packages
Start Date End Date Work Hour People Assigned
Cost
(TL)
1.1 Contact with customer
8.10.2009 8.10.2009 2 Team 30
1.2 Problem Description
8.10.2009 8.10.2009 2 Team 50
1.3 Requirements Gathering
8.10.2009 8.10.2009 2 Team 50
Table 15: Schedule and Budget Allocation for Customer Meeting
Preparing SPMP
WBS Work Packages
Start Date End Date Work Hour People Assigned
Cost
(TL)
2.1 Work Products & Activities
Decomposition
9.10.2009 12.10.2009 4,5 Team 150
2.2 Product Size Estimation
12.10.2009 13.10.2009 5 Team 120
2.3 Process Model 13.10.2009 14.10.2009 3 Team 120
2.4 Resource Allocation
15.10.2009 15.10.2009 2 Team 100
2.5 Schedule Allocation
15.10.2009 15.10.2009 3 Team 50
2.6 Risk Management
Plan
10.10.2009 10.10.2009 2 Team 75
2.7 Technical Process Plans
11.10.2009 11.10.2009 5 Team 109,9
2.8 Supporting Process Plans
14.10.2009 14.10.2009 2 Team 50
2.9 Documentation 9.10.2009 20.10.2009 15 Team 240
Atılım University
COMPE 491-492
29/41
Team # 20 (Team Sheldox)
System Project Management Plan
Version: 1.0
BANK OPERATIONS
2.10 Review of SPMP
22.10.2009 29.10.2009 2 Supervisor 20
2.11 Revised SPMP 30.10.2009 1.11.2009 5 Team 180
2.12 Approval of SPMP
1.11.2009 1.11.2009 - - -
Table 16: Schedule and Budget Allocation for Preparing SPMP
Preparing SRS
WBS Work Packages
Start Date End Date Work Hour People Assigned
Cost
(TL)
3.1 Contact with Customer
8.10.2009 8.10.2009 1 Team 30
3.2 Formal Identification of
User Group
8.10.2009 8.10.2009 2 Team 50
3.3 Product Functions
3.11.2009 9.11.2009 12 Team 190
3.4 Behavioral Requirements Specification
4.11.2009 4.11.2009 3 Team 100
3.5 Non-Behavioral
Requirements Specification
5.11.2009 5.11.2009 2 Team 75
3.6 Documentation 6.11.2009 17.11.2009 10 Team 210
3.7 Review of SRS 18.11.2009 25.11.2009 1 Supervisor 20
3.8 Revised SRS 26.11.2009 29.11.2009 5 Team 200
3.9 Approval of SRS
29.11.2009 29.11.2009 - - -
Table 17: Schedule and Budget Allocation for Preparing SRS
Preparing SDD
Atılım University
COMPE 491-492
30/41
Team # 20 (Team Sheldox)
System Project Management Plan
Version: 1.0
BANK OPERATIONS
WBS Work Packages
Start Date End Date Work Hour People Assigned
Cost
(TL)
4.1 SDD Basic Concepts
20.11.2009 22.11.2009 5 Team 120
4.2 Database Design
25.11.2009 5.12.2009 15 Team 250
4.3 Interface Design
6.12.2009 10.12.2009 10 Team 150
4.4 Algorithms Design
11.12.2009 14.12.2009 10 Team 350
4.5 Network System & Security Design
10.12.2009 15.12.2009 15 Team 270
4.6 Documentation 20.11.2009 15.12.2009 15 Team 300
4.7 Review of SDD
18.11.2009 25.11.2009 1 Supervisor 20
4.8 Revised SDD 26.11.2009 29.11.2009 5 Team 300
4.9 Approval of SDD
26.12.2009 26.12.2009 - - -
Table 18: Schedule and Budget Allocation for Preparing SDD
Preparing STD
WBS Work Packages
Start Date End Date Work Hour People Assigned
Cost
(TL)
5.1 V&V Management
02.01.2010 04.01.2010 4 Team 150
5.2 V&V Acquisition 05.01.2010 07.01.2010 4 Team 150
5.3 V&V Supply 08.01.2010 09.01.2010 4 Team 150
5.4 V&V Development
10.01.2010 12.01.2010 4 Team 150
5.5 V&V Operation 13.01.2010 15.01.2010 4 Team 150
5.6 V&V Maintenance
15.01.2010 17.01.2010 5 Team 177,5
Atılım University
COMPE 491-492
31/41
Team # 20 (Team Sheldox)
System Project Management Plan
Version: 1.0
BANK OPERATIONS
5.7 Documentation 18.01.2010 25.01.2010 10 Team 350
5.8 Review of STD 12.03.2010 15.03.2010 1 Supervisor 20
5.9 Revised STD 20.03.2010 24.03.2010 10 Team 350
5.10 Approval of STD 24.03.2010 24.03.2010 - - 0
Table 19: Schedule and Budget Allocation for Preparing STD
Coding
WBS Work Packages
Start Date End Date Work Hour
People Assigned
Cost
(TL)
6.1 C# 20.02.2010 15.03.2010 2 Team 500
6.1.1 C# User Interface
20.02.2010 25.02.2010 4 Team 200
6.1.2 C# Desktop Application
25.02.2010 28.02.2010 3 Team 150
6.2 Oracle 01.03.2010 15.03.2010 3 Team 1000
6.3 Code REVIEW
15.01.2010 15.03.2010 3 Team 5000
6.3.1 Authorization 12.03.2010 15.03.2010 1 Team 200
6.3.2 User Interface Design
25.02.2010 28.02.2010 1 Team&Supervisor 200
6.3.3 C# & Oracle
integration01.03.2010 15.03.2010 1 Team 300
6.3.4 Report preparation
22.02.2010 15.03.2010 1 - 20
Table 20: Schedule and Budget Allocation for Coding
WBS Work Packages
Start Date End Date Work Hour People Assigned
Cost
(TL)
7.1 Unit Test 10.04.2010 24.05.2010 2 Team 1000
Atılım University
COMPE 491-492
32/41
Team # 20 (Team Sheldox)
System Project Management Plan
Version: 1.0
BANK OPERATIONS
7.2 Integration Test
15.04.2010 25.05.2010 2 Team 2000
7.3 System Test 20.05.2010 24.05.2010 2 Team 1450
Table 21: Schedule and Budget Allocation for Testing.
WBS Work Packages
Start Date End Date Work Hour People Assigned
Cost
(TL)
8.1 Preparation of User Manuel
10.06.2010 10.06.2010 3 Team 100
8.2 Revised User Manuel
10.06.2010 10.06.2010 3 Team 100
Table 22: Schedule and Budget Allocation for User Manuel
WBS Work Packages
Start Date End Date Work Hour People Assigned
Cost
(TL)
9.1 Approval of the product
14.06.2010 16.06.2010 2 Team 0
Table 23: Schedule and Budget Allocation for Deployment
5.3. Control Plan
Any major changes are affected milestones of project and it must be
increase our budget and increase project time. All of the team member will
be responsible for ensuring that projects is completed on time.
Atılım University
COMPE 491-492
33/41
Team # 20 (Team Sheldox)
System Project Management Plan
Version: 1.0
BANK OPERATIONS
5.3.1. Requirements Control Plan
Before the defining of requirements we will arrange meeting between our
team and our customer. Since the customer is sure about what they want,
there won’t be any modification on the requirements.
5.3.2. Schedule Control Plan
We arrange meetings between our team and our customer when we find
suitable time for us. The progress of the work will be observed by the
customer and our supervisor in those meeting. All team members should
attend the each meeting. If there is a extraordinary situation, he will not
attend, but in future we will tell each discussions about the meeting to him.
The estimated delivery dates are decided by our supervisor.
5.3.3. Quality Control Plan
We arrange meetings above our customers and in each meeting we will
show our works to them. Each project progress will be observed by KBC
Bank employees. In every meeting we should take advices from KBC Bank
and our supervisor. As a result, we want to increase quality of our project.
5.3.4. Reporting Plan
We defined the project deliverables in the section 1.1.3. The deliverables
are announced from our project web site. These deliverables will be
reviewed both our supervisor and KBC Bank. We will announce if there are
any changes in the deliverables. Each version or update or updated of
deliverables are available in our web site. Each of report is checked by our
configuration managers.
5.3.5. Metrics Collection Plan
Metric collection will be made a comparison between what is build and what had built, so
we anticipate the error happening, delay happening and then extra cost estimation. These
will references to us.
Atılım University
COMPE 491-492
34/41
Team # 20 (Team Sheldox)
System Project Management Plan
Version: 1.0
BANK OPERATIONS
5.4. Risk Management Plan
During the project we will expected some risks. We must cope with these
problems. Otherwise, our project lifecycle become trouble. High probability risks
that occur during project;
Disagreement between team members
During the project lifecycle there are some arguments in the team
members’ opinions. Add them up, one of the project members not attend
the meetings, it will causes arguments between team members. In this
case, we will make a meeting and we will determine the result. If we will not
determine the result, we will discuss with project’s supervisor.
Unavailability of team members
All the team members are irregular, so members take different courses.
Every member has different weekly course schedule. In addition to this, we
will arrange meeting between KBC Bank so; our meeting schedule is set by
KBC Bank. For this reason, all the team members may not be exists in
every meeting. We decide at least one of the team member join meeting
and he will talk us all of the meeting subjects and decisions.
Lack of experience working with customer
Team members do not have enough experience for meeting and
understanding customer’s problems. It will need good communication
between customer and team members. The requirements should be well
defined and understandable by all of the team members. For this kind of
situations we always communicate with customer by e-mail or meetings.
Atılım University
COMPE 491-492
35/41
Team # 20 (Team Sheldox)
System Project Management Plan
Version: 1.0
BANK OPERATIONS
Lack of training on user panels
Bank operations project software parts depends on c# and oracle. If some
of the team members have no experience on both c# and oracle, we will
face with some problems during the development of software. Learning and
using these concepts will be creating a risk on project. As a result, all of the
team members should make a deep search about these languages and
learn how to create applications so we decrease the probability of risk. If
we face with very big problem during coding, we should take our
supervisors opinion and apply them.
Testing the product
All the end of the coding, we must test our product for bugs and errors
which effected the system directly. It is difficult to test every situation.
Testing has very important role for the project. As a result, we should spare
more time for testing and all team members should do their responsibility
about this part by obey the test plan.
Separation of a team member from the group
The project team composed of 3 members and there is a very big problem
among the group member which is separating. During the project, any team
member may leave the project. It has lots of reason such as illness,
psychological problems, or leaving the school such as economic conditions
or family problems. If one of the member leave from the group our
members should share the remaining works and they strive for finishing the
project on the defined deadline of the project.
Atılım University
COMPE 491-492
36/41
Team # 20 (Team Sheldox)
System Project Management Plan
Version: 1.0
BANK OPERATIONS
6. Technical Process Plans
6.1. Process Model
In the project, we discuss and determined to use Iterative model because in
our project. We should turn back a lot during the development of software.
It means that the requirements are not stable, so we may change during
the project lifecycle. Since iterative is a model which does allow retrieving
back at any phases, discuss and we think iterative is a model which allows
turning back at any phases, we discuss and we think iterative model is fits
for the project. As a result appropriate process is iterative for our project.
6.2. Methods, Tools, and Techniques
During the first semester, we should finish the documentation. All of the
Software Project Management steps are applied and all revision steps will
be shown in different version of project. There should be some minor and
major changes. In second semester coding and network system will be
completed. We define the tools and techniques which are using during the
project as shown below;
SW Tools: PHP, Oracle, C#, MS Office, MS Project, Mozilla Firefox 3.
HW Tools: Personal computers, laptops and a database server.
6.3. Infrastructure Plan
In order to develop Bank operations system, C# is used in user interfaces, Oracle Is used
for DMBS, HTML & PHP is used for web site. During the project we use some resources
which are free for us such as sources for understanding and learning new things.
Places for studies and developing project will be determined by the Project Manager. PM
talks every member and determines a time which is most suitable for every team member.
These places may be one team members’ house, school’s studying room and a café
which is located in Balgat.
Atılım University
COMPE 491-492
37/41
Team # 20 (Team Sheldox)
System Project Management Plan
Version: 1.0
BANK OPERATIONS
6.4. Product Acceptance Plan
The project is controlled by the supervisor and the customer. And they determine the
missing points of the project. The project is repeated until supervisor and customer
satisfaction is ensured. So we guarantee to develop the product that the customer really
needs. For the finally we will present to the customer and the supervisor. If it is necessary,
we will change some points of product.
Atılım University
COMPE 491-492
38/41
Team # 20 (Team Sheldox)
System Project Management Plan
Version: 1.0
BANK OPERATIONS
7. Technical Process Plans
7.1. Configuration Management Plan
The project can have changes. If there is a change requirement from customer or
supervisor, it will be updated to a new version of report. The first deliverable one is version
1 like SPMP V1.0. If changes come, it will be SPMP V2.0 which is updated.
7.2. Quality Assurance Plan
All deliverables should be prepared by following IEEE standard. Meeting frequencies
should be well organized between customer and supervisor. Team members should follow
the schedule strictly. The project steps should be completed in convenient time.
7.3. Documentation Plan
The documentation is based on IEEE standards. The IEEE standard requires SPMP,
SRS, SDD and STD. These deliverables will be received by supervisor.
Deliverable work products will be documented and delivered according to distribution list
on due date.
7.4. Deployment Plan
Firstly, we develop a plot program and we will set up it into two bank agency, then we will
wait for result. Due to the result, we make a decision. If our plot program works perfectly,
we will distribute the system in other bank agencies.
7.5. Review Plan
The team will review the document as deliverables. All deliverables will update at the web
site so the supervisor will take a chance to reach to the deliverables via internet.
Atılım University
COMPE 491-492
39/41
Team # 20 (Team Sheldox)
System Project Management Plan
Version: 1.0
BANK OPERATIONS
Appendices
Appendix 1
End User Efficiency:
Our system makes easier the usage of user interface for last user. Operations have done
faster. On line operations provided emphasize a design for end user efficiency. They
include:
Menus
Search box
Hard copy user documentation
Easy navigation between user interfaces
Automated cursor movement
It will be updated when the requirements are completed.
Appendix 2
Cocomo:
Coefficients for basic COCOMO:
Software project ab bb cb db
Organic 2.4 1.05 2.5 0.38
Semi-detached 3.0 1.12 2.5 0.35
Embedded 3.6 1.20 2.5 0.32
Atılım University
COMPE 491-492
40/41
Team # 20 (Team Sheldox)
System Project Management Plan
Version: 1.0
BANK OPERATIONS
Appendix 3:
Gantt chart
The team will update STD part on web site soon. The team can’t communicate with a
member because of health problem. In addition to this, we can’t estimate the second
semester’s dates.
Atılım University
COMPE 491-492
41/41
Team # 20 (Team Sheldox)
System Project Management Plan
Version: 1.0