SE-Lab Roll no: 1604178

Practical:1

Aim: To draft a project plan

1. Click on start menu and then click on rational requisite pro.
2. Click on file new project.
3. Click on blank ok.

4. A screen will appear. Write the name of the project and click on browse and select the place where you want to save this
project. Then click on ok.

1
SE-Lab Roll no: 1604178

5. A dialogue box will appear. Click yes and another dialogue box will appear .Click on close.

2
SE-Lab Roll no: 1604178
6. The project name will display on the left side of the screen.

7. Right click on project. Click on newpackage.

8. Package properties dialogue box will appear. Write the name as functional, non_functional , stakeholder, use_case and
click on ok.

3
SE-Lab Roll no: 1604178
9. All the packages will display on the left side of the screen.

10. Click on fileproject administrationproperties.

4
SE-Lab Roll no: 1604178
11. A project properties dialogue box will appear.Click on requirement typesadd.

12. Add name functional, non_functional, stakeholder, usecase and requirement tag prefix & Click on ok.

5
SE-Lab Roll no: 1604178
13. Right click on packagerequirement. A requirement properties dialogue box will appear.

14. Add name and click ok.

6
SE-Lab Roll no: 1604178

Practical:2

Aim: To track the progress of the project.

1. Start rational requisite pro.
2. Click on fileopen project.
3. Click on use_case packagenewrequirement.

4. A screen will appear.Click on general and add name as manager.

7
SE-Lab Roll no: 1604178
5. Click on traceabilityaddok.

6. Right click on usecasenewview.

8
SE-Lab Roll no: 1604178

7. A following screen will appear.Write name as manager.Click view type as attribute matrix,tracebility matrix,tracebility
tree.Click on OK.

8. Attribute matrix will appear as:

9
SE-Lab Roll no: 1604178

9. Tracebility matrix will appear as:

10. Traceability tree will appear as:

10
SE-Lab Roll no: 1604178

11. Click on usecasenewrequirement.Write name as credit and type as non_functional and click on tracebility and click
ok.

11
SE-Lab Roll no: 1604178

12
SE-Lab Roll no: 1604178

12. The various view will appear as:

13
SE-Lab Roll no: 1604178

14
SE-Lab Roll no: 1604178

Practical-3

Aim: Preparation of SRS document and test plan document.

1. Open the project.

2. Click on fileproject administrationproperties.

3. Click on document types and add the document type.

4. Write name ,file extension and default requirement type and then click ok.

15
SE-Lab Roll no: 1604178

5. Click on functionnewdocument.

16
SE-Lab Roll no: 1604178

6. Write name and select document type and click ok.

7. The SRS document will appear.

17
SE-Lab Roll no: 1604178

8. Proceed the same steps with non_functional,usecase and stakeholder.

Practical:4

Aim: Preparation of software configuration management and risk management related document.

Software configuration management:

Software configuration management, SCM is an activity which is used at every level and every part of the process of
software Engineering. Every improvement takes the shape of better control. This is a discipline which controls betters and
according to client need in software Engineering. With the help of this many types are changes which play an important
role in software Engineering and development process.

In the simple way if we define the term configuration of management, this is the tool which makes better control, easy
maintenance during the whole process of software development. With the help of software configuration management we
can easily find out what modification and controlling required by the developer. SCM have the capacity to control all those
effects which comes in software projects. The main objectives of SCM is increase the production by reduce the errors.

When a software development process start then SCM take change by identification, control, alteration, audit and etc. after
that the output of total process provided to our customer. We can clarify the action of SCM as:

Software configuration identification - Normally software is used in various kinds of programs and documentation and
data related to each program is called configuration identification. With the help of C.I we can make a guide line which will
be helpful in software development process, several time the requirement of guideline for check the document and design
of software. Document related to SCM are the useful item, with the help of this we can make better control and take a basic
unit for configuration.

Software configuration control - This is the process of deciding with the help of this we make coordination between the
changes which is necessary and apply them as per mentioned in guideline. Configuration control board gives the
permission for any kind of change or modification which is necessary for the project. Many times CCB take advice of those

18
SE-Lab Roll no: 1604178
members which are the part of software development process.

Accounting status of Software configuration - The process of maintaining record of all data which is necessary for the
software is called accounting status of software. It has all the data related to the old software to new software that what
changes are done or required for the fulfillment of the customer need.

Auditing of software configuration - Auditing of software configuration is may be defined as an art with the help of this
we can understand that the required actions or changes are done by the developer or not. Some of the item involved in the
process of verifying or auditing.

 Function is properly performed by the software.

 The process of documentation, data is completed or not.

Benefits

 With the help of SCM we can easily control all changes which are done in development process.

 It gives the surety to check that changes are done on required area.

 It is helpful to generate the new software with old components.

 SCM has the capacity to explain everything about the process of software development.

Risk Management:
Risk is an expectation of loss, a potential problem that may or may not occur in the future. It is generally caused due to
lack of information, control or time.A possibility of suffering from loss in software development process is called a
software risk. Loss can be anything, increase in production cost, development of poor quality software, not being able to
complete the project on time. Software risk exists because the future is uncertain and there are many known and unknown
things that cannot be incorporated in the project plan. A software risk can be of two types (a) internal risks that are within
the control of the project manager and (2) external risks that are beyond the control of project manager. Risk management
is carried out to:

1. Identify the risk

2. Reduce the impact of risk
3. Reduce the probability or likelihood of risk
4. Risk monitoring

A project manager has to deal with risks arising from three possible cases:

1. Known knowns are software risks that are actually facts known to the team as well as to the entire project. For
example not having enough number of developers can delay the project delivery. Such risks are described and included
in the Project Management Plan.
2. Known unknowns are risks that the project team is aware of but it is unknown that such risk exists in the project or not.
For example if the communication with the client is not of good level then it is not possible to capture the requirement
properly. This is a fact known to the project team however whether the client has communicated all the information
properly or not is unknown to the project.
3. Unknown Unknowns are those kind of risks about which the organization has no idea. Such risks are generally related
to technology such as working with technologies or tools that you have no idea about because your client wants you to
work that way suddenly exposes you to absolutely unknown unknown risks.

Software risk management is all about risk quantification of risk. This includes:

1. Giving a precise description of risk event that can occur in the project
2. Defining risk probability that would explain what are the chances for that risk to occur
3. Defining How much loss a particular risk can cause

19
SE-Lab Roll no: 1604178
4. Defining the liability potential of risk

Risk Management comprises of following processes:

1. Software Risk Identification

2. Software Risk Analysis
3. Software Risk Planning
4. Software Risk Monitoring

These Processes are defined below.

Software Risk Identification:

In order to identify the risks that your project may be subjected to, it is important to first study the problems faced by
previous projects. Study the project plan properly and check for all the possible areas that are vulnerable to some or the
other type of risks. The best ways of analyzing a project plan is by converting it to a flowchart and examine all
essentialareas. It is important to conduct few brainstorming sessions to identify the known unknowns that can affect the
project. Any decision taken related to technical, operational, political, legal, social, internal or external factors should be
evaluated properly.

In this phase of Risk management you have to define processes that are important for risk identification. All the details of
the risk such as unique Id, date on which it was identified, description and so on should be clearly mentioned.
Software Risk Analysis

Software Risk analysisis a very important aspect of risk management. In this phase the risk is identified and then
categorized. After the categorization of risk, the level, likelihood (percentage) and impact of the risk is analyzed. Likelihood
is defined in percentage after examining what are the chances of risk to occur due to various technical conditions. These
technical conditions can be:
1. Complexity of the technology
2. Technical knowledge possessed by the testing team
3. Conflicts within the team
4. Teams being distributed over a large geographical area
5. Usage of poor quality testing tools

With impact we mean the consequence of a risk in case it happens. It is important to know about the impact because it is

20
SE-Lab Roll no: 1604178
necessary to know how a business can get affected:

1. What will be the loss to the customer

2. How would the business suffer
3. Loss of reputation or harm to society
4. Monetary losses
5. Legal actions against the company
6. Cancellation of business license

Level of risk is identified with the help of:

Qualitative Risk Analysis: Here you define risk as:

 High
 Low
 Medium

Quantitative Risk Analysis: can be used for software risk analysis but is considered inappropriate because risk level is
defined in % which does not give a very clear picture.

Software Risk Planning:

Software risk planning is all about:

1. Defining preventive measure that would lower down the likelihood or probability of various risks.
2. Define measures that would reduce the impact in case a risk happens.
3. Constant monitoring of processes to identify risks as early as possible.

Software Risk Monitoring

Software risk monitoring is integrated into project activities and regular checks are conducted on top risks. Software risk

21
SE-Lab Roll no: 1604178
monitoring comprises of:

 Tracking of risk plans for any major changes in actual plan, attribute, etc.
 Preparation of status reports for project management.
 Review risks and risks whose impact or likelihood has reached the lowest possible level should be closed.
 Regularly search for new risks

22