Software engineering

unit I

Project management process/Phases of Management Process

The activities in the management process for project can be broadly divided into three phases: 1. Planning 2. Monitoring and control and 3. Termination analysis

Planning:
The project plan management. provides fundamental basis for project

A software plan is produced before the development activities begins and is updated as development proceeds. Key tasks are: Cost and schedule estimation Project staffing Controlling and monitoring plans Quality control plans

Monitoring and control:

Lasts for the duration of the project and covers the development process Monitors all key parameters like cost, schedule, risks Takes corrective action when needed Needs information on the development process-provided by metrics

Termination analysis:
1

Software engineering

unit I

Termination analysis is performed when the development process is over Basic purpose: o To analyze the performance of the process, and identify lessons learned o Improve predictability and repeatability o Central to a learning organization or culture

The Inspection process

The main goal of the inspection process is to detect defects in work products. Some of the characteristics of inspections are: An inspection is conducted by technical people for technical people. It is a structured process with defined roles for the participants.
2

Software engineering

unit I

The focus is on identifying problems, not resolving them The review data is recorded and used for monitoring the effectiveness of the inspection process

Inspections are performed by a team of reviewers including author , one of them being moderator. The different stages in this process are: planning, preparation and overview, group review meeting and rework and follow-up. These stages are generally executed in a linear order.

Planning:
The objective of planning is to prepare for inspection. The author of work product ensures that the work product is ready for inspection. The moderator checks the entry criteria are satisfied by the work product The review team is also formed in this phase. The package that needs to be distributed to the review team is prepared.

Overview and preparation:

The main task in this phase is for each reviewer to do a self-review of the work product. A reviewer goes through the entire work product and logs all the potential defects he or she finds. The reviewer also record the time spent in the self review.

A standard form is given (refer notes)

Group review meeting:

The basic purpose of group review meeting is to come up with the final defect list, based on the initial list of defects reported by the reviewers and the new ones found during the discussion in the meeting.
3

Software engineering

unit I

A team leader (called the reader) goes over the work product line by line and paraphrases each line to the team. At any line, If any reviewer has any issue, he raises the issue. After discussion an agreement is reached and one member of the review team (called the scribe) records the identified defects in the defect log. At the end the scribe reads out the defects recorded for the final review by the team members. A standard form is given (refer notes)

Rework and follow up:

In this phase the author corrects all the defects raised during the inspection.

Roles and repobsilities:

The responsibility of moderator: Schedule group review meeting Ensure all participants are prepared and have submitted self review log Conduct group review meeting Ensure that meeting stays focused on defect identification Ensure that group review reports are completed

The main issues for a reviewer are: Be prepared for group review Be objective; focus on issues not people Concentrate on problems

Software engineering

unit I

Guidelines for work product:

Though the inspection process is same, focus on inspection is different for different products. The constitution of review team and checklist depends on nature of work product.

Some guidelines are as below: Work product Focus of inspection Participants

Requireme Requirements meet customer needs Customer nt Requirements are implementable Designers specificatio n Omissions, inconsistencies and ambiguities Tester in the requirements Developer High level design High-level design implements the requirements The design is implementable Omissions, and other defects in the design Code Code implements the design Code is complete and correct Defects in code Requirements author Detailed designer Developer Designer Tester Developer

Software engineering

unit I

System test The set of test cases checks all conditions in Requirements cases the requirements author Test cases are executable Tester Project leader Project manageme nt plan Plan is complete Project leader

Project management plans is implementable SEPG member Omissions and ambiguities Another project leader

Software configuration Management process

Definition of SCM:
Software configuration management is the discipline of managing the evolution of complex software systems It is also defined as the process of controlling and monitoring change to work products CM functionality a proper CM process does the following: Give latest version of a program-suppose that a program has to be modified. the modification has to be carried out in the latest copy of that program. Undo a change or revert back to a specified version- a change is made to a program, but later it becomes necessary to undo this change request. Prevent unauthorized changes or deletions- a programmer may decide to change some programs only to discover that the change has adverse side effects. Gather all sources, documents and other information for the current system-all sources and related files are needed for releasing the product. and also sometimes needed for reinstallation.

CM mechanisms Configuration identification and base lining - it forms a reference point in the development of system. It is the arrangement of set of
6

Software engineering

unit I

SCIs(software configuration item- is a document that is explicitly placed under configuration control and can be regarded as a basic unit for modification. Version control or version management- it helps to preserve the older versions of the program whenever programs are changed. Access control- to understand access control we need to first understand the lifecycle of SCM

working

under review

under SCM

SCI is considered to be in working state when it is under development and not visible. hence it is considered "frozen" it is under review when reviewers check it for the quality and changes. if the item is not approved it goes back to working state. if approved its in library where unauthorized users cannot change it.

CM process Set of activities that need to be performed to control change. here first step is planning the configuration controller (CC) is responsible for the implementation of the CM plan. when there is a large team when 2 or more teams are involved in development of same software , it is necessary to have a configuration control board(CCB)

Requirements change management process changes in the requirements can come at any time during the life of a project the change management process has the following steps:
7

Software engineering

unit I

Log the changes Perform impact analysis on the work products Estimate impact on effort and schedule Review impact with concerned stakeholders Rework work products

Process management process continuously improving process predictable process standard consistent process Disciplined process
initial(1) repeatable(2 ) defined(3) managed(4) optimizing(5 )

Improving the quality and productivity of the process is the main objective of the process management process. which in turn improves the quality and productivity of the product. The concept of introducing changes in small increments based on the current state of the process has been captured in the capability maturity model (CMM) framework. Software process capability describes the range of expected results that can be achieved by following the process
8

Software engineering

unit I

A maturity level is a well defined evolutionary plateau towards achieving a mature software process.

The CMM suggests that there are five well defined maturity levels of a software process. 1. initial process: is an ad hoc process that has no formalized methods for any activity 2. repeatable process: based on the past experience with similar projects cost and schedule are tracked, problems resolved, software project standards are defined and followed. 3. defined level: each step is carefully defined with verifiable entry and exit criteria, methodologies for performing the step, and verification mechanism for the output of step. 4. managed level: data is collected from software processes, which is used to build models to characterize the process. 5. optimizing level: focus is on process improvement. data is collected and analyzed. new technology and tools are introduced to strengthen the quality, productivity and performance.