Docstoc

CM

Document Sample
CM Powered By Docstoc
					                                   Index



1.     Introduction   …………………………………………………………………                        1
     1.1. Purpose of this Document ……………………………………………………                2
     1.2. Overview of Provision …………………………………………………………                 2
     1.3. Scope of this Document…………...……………………………………………               2
2.     Organization of Configuration Management (CM)
     2.1 Organization ……………………………………………………………………… 3
     2.2 Responsibilities……………………………………………………………….…                    3
3.     Configuration Management (CM) Process
     3.1 Identification ………………………………………………………………….… 4
     3.2 Configuration Control…………………………………………………………… 5
     3.3 Version Control……………………………………………………………………5
     3.4 Logging Configuration Status…………………………………………………           6
     3.5 Auditing…………………………………………………………………………. 6
4.     Project Schedule ………………………………………………………………… 6
5.     Tools and Methods for Configuration Management Plan……………………… 7
6.     Plan Optimization……………………………………………………………… 8




                                                                        1
1.      Introduction

This document is prepared for identifying the configuration management (CM) activities of
our project management tool PROVISION.


1.1        Purpose of This Document

This document is intended to include identification of the components and structures;
Controlling releases and changes; validating completeness and ensuring the life-cycle model
of the program.


1.2. Overview of PROVISION

PROVISION is designed to be a new software for companies workgroups or individuals
who want an online control mechanism over their project which is secure and easy to use.
The main features of PROVISION can be listed as follows:
           -   Project Scheduling
           -   Gantt Chart Construction
           -   Group based and individual task assignment
           -   Project status overview
           -   Resource management
The main properties will include
           -   Multi-user support
           -   Online viewing and editing the information of the projects
           -   Security options to make the resources safe


1.3. Scope of This Document

This document is prepared by Netsoft team to ensure the following:


                                                                                              2
           -   Effective update control is established and maintained
           -   Team members are aware of the changes done in the project
           -   Project documentation is gathered, classified and recorded systematically




2.      Organization of CM

2.1. Organization

Since we have a small team and all team members are participating in generating the source
code we don’t need a detailed organization. All the CM activities are controlled, rewritten and
Published by all members of Netsoft team



2.2. Responsibilities

The general timeline of the project has been produced by the Netsoft team but all the team
members are free to arrange his schedule as long as his schedule doesn’t conflict with the
general timeline. All team members have to inform the major changes he is planning to do on
the project. Major changes in the project should be decided as a team, however all team
members are free to decide on and implement minor changes in his field of interest. This
approach makes the source code generation faster. As an example the main features of our
interface is decided by our team. However many minor changes on the interface are decided
and implemented by the person who is responsible for preparing the interfaces of
PROVISION which is Ömer KARADUMAN.




                                                                                              3
3.      Configuration Mangement Process

The Netsoft team has decided to divide the CM process into the following tasks:
             -   Identification
             -   Configuration Control
             -   Version Control
             -   Configuration Status Accounting
             -   Auditing

3.1. Identification

In this process the configuration items are identified by the Netsoft team. We have decided on
the following configuration items:


             -   Software
             -   Documents
             -   Baselines
Software:
The project development environments, programming language libraries, editors, compilers,
web development tools. The provision team decided to use the recent versions of the
development tools to make use of the newest features they provide. But this also came up with
some problems because some of the tools we used are still in development phase.


Documents:
When one part of the project is developed, related documents of this part is generated by the
team members.


Baselines:


The important points of the project at the development phase constitute the baselines.
These points constitute milestones at the development of our project.




                                                                                                4
3.2. Configuration Control


Before we have started to implement PROVISION we tried to specify all the details. However
it is impossible to all specify all the details. Moreover some new ideas may occur during the
development phase. In such cases, in order to keep it systematic, we should establish a change
mechanism. The change mechanism we used can be explained in the following topics:


        Change Request:
If a member thinks that a change is needed and should be done he should inform other
members of the team about the change he is willing to do. Generally this information process
is done during the weekly meeting of the team, which is held every Sunday of the week


        Request Analysis and Approval:
After one of the team members requests a change, the team discusses it. Team considers the
advantages and disadvantages of the change(s) to be done. If the advantages of the change(s)
is/are considerable more then the disadvantages the request is approved by the team. if not it
is rejected.


        Implementing the Change(s):
After the approval, the team leader (Seren SERT) charges the people who are responsible for
the part of the project, on which some changes are intended to be done.


3.3. Version Control

We did version controlling by using the CVS which is provided by our department.
The following steps are as follows:
               -   All team members use CVS while generating source code
               -   Completed codes are uploaded to the CVS server and all other members
               -   The developer is informed about the changed parts of a code segment that he
                   has generated.




        Version Numbering


                                                                                                 5
       As we said before there can be changes in the project. We can classify these changes
into two categories: major changes and minor changes.
       Our versions include two numbers separated by a dot. The first number indicates the
major changes and the second number indicates the minor changes in the project.
       As an example the version number 1.3 indicates that it’s the firs version of the
program and there 3 small changes has been made on the program.




3.4. Logging Configuration Status
 To keep the team connected and be aware of the changes done on the project we followed
the steps listed below:
           -   We held meetings regularly (one per week at least)
           -   We construct an e-mail group to make communication faster
           -   We used CVS to reach the recent files and version controlling


All the files included in the project are kept in CVS. This serves as a backup utility. Moreover
When a change occurs in any changes in a code fragment CVS alerts relates team members
about the change.


3.5. Auditing
Functional Configuration Audit will be performed. The main aim of Functional Configuration
Audit is to verify that the development of a configuration management has been completed
successfully and the configuration item has achieved the desired performance and functional
characteristics specified before.


Functional audit is performed at the end of each development process.



4.      Project Schedule


ID Task Name               Duration       Start          Finish     Resource Names




                                                                                               6
1 DESIGN               54 days   Tue 15.02.05 Fri 29.04.05   NetSoft

2 Class Definitions    14 days   Tue 15.02.05 Fri 04.03.05   Bilen Yavuz

     Library Object
3                      14 days   Mon 07.03.05 Thu 24.03.05 NetSoft
     Creation

4 Component Creation 14 days     Wed 23.03.05 Mon 11.04.05 NetSoft

                                                             Ömer Karaduman, Bilen
5 Screen Modules       15 days   Mon 11.04.05 Fri 29.04.05
                                                             Yavuz

6 Presentation Layer   5 days    Tue 15.02.05 Mon 21.02.05 Ömer Karaduman

     Authorization &                                         Ömer Karaduman, Seren
7                      5 days    Thu 31.03.05 Wed 06.04.05
     Validation                                              Sert

     Bussiness Logic
8                      5 days    Wed 23.02.05 Tue 01.03.05 Bilen Yavuz
     Layer

9 Encyription Layer    12 days   Tue 15.03.05 Wed 30.03.05 Özgür Doğuş Sönmez

                                                             Seren Sert, Özgür Doğuş
10 Data Access Layer   4 days    Wed 02.03.05 Mon 07.03.05
                                                             Sönmez

11 Store Procedures    3 days    Mon 07.03.05 Wed 09.03.05 Seren Sert

12 First Demo          1 day     Thu 10.03.05 Thu 10.03.05 Netsoft

     Testing &
13                     4 wks     Tue 03.05.05 Mon 30.05.05 NetSoft
     Debugging

14 First Version       1 day     Mon 02.05.05 Mon 02.05.05 NetSoft

15 Testing             43 days   Tue 03.05.05 Thu 30.06.05 NetSoft

16 Debugging           38 days   Fri 01.07.05   Tue 23.08.05 NetSoft




5. Methods for Software Configuration
Management (SCM)



                                                                                       7
In every SCM activity we follow the criteria listed in the SCM process criteria part. Since we
have a very small team, every team member is very important at each phase of the project,
because of this every member has to participate in the SCM meetings. All the decisions about
the project have to be made as a team and all the members should be notified about the
changes done on the project. We can list the main rules that all members should obey as
follows:


           -   All team members should try to follow software engineering standards as much
               as he can.
           -   All members should inform the others about the changes he has done
           -   For assessing the technical correctness formal technical review should be done
               by group members.
           -   All team members must be sure that related software configuration item is
               updated regularly.




   6. Plan Optimization
As the project development goes forward, some changes in the plan may be changes in order
to meet the needs that are likely to occur in the development phase.




                                                                                                 8

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:19
posted:11/26/2011
language:English
pages:8