software project management lab manual

KUMARAGURUCOLLEGE OF TECHNOLOGY

COIMBATORE-641006

SOFTWARE DEVELOPMENT LAB

--------------------------------------------------

LABORATORY MANUAL

DEPARTMENT OF MCA

1

CONTENTS

Exercise no. Title of the Exercise Page no.

I Rational Administrator 3

II Vision Document 11

III Use Case Document 20

IV Requirement Management Plan 24

V Use Case Diagram 38

VI Sequence Diagram 43

VII Collaboration Diagram 47

VIII Activity Diagram 50

IX Rational Purify 54

X Rational Quantify 57

XI Rational Robot 62

XII Rational Test Factory 66

XIII Rational Test Manager 70

2


LABORATORY MANUAL

Exercise/Experiment Number: 1

Lab Code / Lab : Software development lab

Course / Branch : MCA.

Title of the exercise/experiment : Rational Administrator

______________________________________________________________

STEP 1: INTRODUCTION

a) OBJECTIVE OF THE EXERCISE/EXPERIMENT

To create groups and users after setting the project with appropriate requirement

and test data sources. The groups are like manager, tester and test designer.

Also the users are to be assigned to appropriate groups.

STEP 2: ACQUISITION

(The full material for the following topics is to prepared)

b) Facilities/material required to do the exercise/experiment:

Sl.No. Facilities/material required Quantity

1 P IV 3.0 GHZ 2GB DDR

RAM 80 GB HDD MACHINE

60

2 TURBO C 60

3

c) Procedure for doing the exercise/experiment:

Steps Description (in full)

1 Open Rational administrator by clicking start

Programs Rational software Rational

administrator.

2 Select File new Project and enter the project

name and location.

3 Enter the password with which we can connect

to, configure or delete the project.

4 Read the summary of the project settings

provided and configure the project and click the

finish button.

5 If the configure project now option is selected ,

the configure project dialog box opens.

6 Create an associated requisitepro project with

the required template.

7 Create an associated Test Data source- choose

the type of data store.

8 Right click and select the connect option on the

project name.

9 Create test group by right clicking test group (in

tree structure) and selecting the Insert Test

Group option.

10 Name the test group and set it as default group

and edit the privilege based on the need.

11 Create a Test user by right cliking test user(in

the tree structure) and selecting the insert test

user option.

12 Enter the user ID and other necessary details.

4

And click ok, the test user is created.

Note:

d) Calculations

Not applicable.

e) Inference and analysis:

5

STEP 3: PRACTICE/TESTING

Questions with answers:

Use the Rational administrator and do the following work.

a) Create the following test groups and assign group permissions.

i) Managers ii) Testers iii) Test Designers

b) Create five users and attach them to appropriate groups.

1. Note: Furnish suitable descriptions wherever required

10


LABORATORY MANUAL


Lab Code / Lab : P07CA504 Software development lab.


Title of the exercise/experiment : Vision Document.

______________________________________________________________



To prepare a vision document for a project using Rational requisite pro.

STEP 2: ACQUISITION






60

2 TURBO C 60



1 Open Rational Requisitepro by clicking Start

11

ProgramsRational Software Rational

Requisite pro,

2 Select FileNew Project and enter the project

name and location.

3 Right click the Features and vision document in

the left pane.

4 Select NewDocument Enter document name

5 Double click the newly created vision document.

6 Edit the template based on the project and add

requirements.

7 Save the document.

Note:

(Diagrams like circuit diagrams, chart like process charts and so on are to be

provide as per the requirement of the exercise.)

d) Calculations

Not applicable.

e) Inference and analysis:(Sample document of Keyboard typing tutor.

Keyboard Typing TutorKUMARAGURU

Version 1.0

12

Revision History

Date Version Description Author

10/07/2009 1.0 Initial Release N.Jayakanthan

13

Table of Contents

1. Introduction 1

1.1 Purpose 11.2 Scope 11.3 Definitions, Acronyms and Abbreviations 11.4 References 1

2. Positioning 1

2.1 Business Opportunity 12.2 Problem Statement 12.3 Product Position Statement 1

3. Stakeholder and User Descriptions 2

3.1 Stakeholder Summary 23.2 User Summary 23.3 Key Stakeholder / User Needs 2

4. Product Overview 2

4.1 Summary of Capabilities 2

5. Product Features 2

5.1 Login 25.2 Course 5.3 Sentence drills 35.4 Paragraph drills 35.5 Free drills 35.6 Game 3

6. Constraints 3

7. Quality Ranges 4

8. Other Product Requirements 4

8.1 System Requirements 4

9 Documentation Requirements 4

9.1 User Manual 4

14

KUMARAGURU1. Introduction

The purpose of this document is to collect, analyze and define high-level needs and features of the Keyboard Typing Tutor. It focuses on the capabilities needed by the stakeholders, and the target users, and why these needs exist. The details of how the Keyboard Typing Tutor fulfils these needs are detailed in the use-case and supplementary specifications.

1.1 Purpose

This system serves as a guide to learn fingering in a quick and more efficient manner. The primary objective of the project, Keyboard Typing Tutor is to devise software which acts as a very good platform to people who wishes to train them in fingering.

1.2 Scope

In view of the fact that the versatility and speed is growing to be the most important factor of any system, the need of any such system comes into the picture. Computerized system possesses these properties and it is very useful. All the above criteria are met in this project to reduce all the uncertainty.

1.3 Definitions, Acronyms and Abbreviations

See the glossary.

1.4 References

www.w3school.com www.knowledgeisland.com

2. Positioning

2.1 Business Opportunity

The Keyboard Typing Tutor is used to reduce the complexity of learning the fingering. The traditional process will take more time, very less efficiency, so we go in for the next level of learning.

With the various levels of typing offered, the user can learn fingering in an efficient way by moving across various levels and test their skills when needed.

2.2 Problem Statement

The problem of The manual training process.

affects Students and other users.

The impact of which is Time consuming and less efficiency.

A successful solution would Calculating the accuracy percentage and speed.

15

2.3 Product Position Statement

For Students

Who Wish to improve their typing speed

The Keyboard Typing Tutor is a software

That Enables quick and efficient learning

Unlike The existing manual training

Our product Provides in-built features to keep a check on accuracy and speed

3. Stakeholder and User Descriptions

This section describes the users of the Keyboard Typing Tutor. The users of the Keyboard Typing Tutor: the students and others who wish to learn typing.

3.1 Stakeholder Summary

Name Role

Students Ensures that their typing skills has improved.

3.2 User Summary

Name Description Stakeholder

Students Learns typing in a quick and more efficient way.

Self-represented

3.3 Key Stakeholder / User Needs

A User Survey was conducted to determine the user problems with the existing system and to solicit user input on improvements. The complete survey results are included in the Stakeholder Requests Document. A summary of the survey results are listed below in order of relative importance from high to low

Need Priority Concerns Current Solution Proposed Solutions

Quick learning High Time intensive work

The students have to take up courses to learn typing.

Computerized system which eases the learning process.

Efficiency High Inefficiency The typing efficiency cannot be effectively measured.

Computerized system which calculates the typing efficiency then and there.

16

4. Product Overview

4.1 Summary of Capabilities

Customer Support System Customer Benefit Supporting FeaturesEasy to use The system provides a very good user interface that

can be accessed by any user.Quick and Efficient learning Making the user interface easy, eventually makes the

learning process quick.

Accuracy calculations ensure efficiency.

5. Product Features

5.1 Login

The system prompts for a user name. This is done to keep track of the sessions.

5.2 Course

Provide effective help

Indicate mistakes

Calculate accuracy

Highlight the key to be typed and the finger to be used

The system should provide a full course that enables the user to train him with the basic characters and its combinations. Efficient help should be provided by displaying a sample of a computer screen and a keyboard. This will be helpful in knowing about the arrangement the keys in the keyboard. The tutor should also provide visual aid to the user by highlighting the key to be typed in the keyboard and the finger to be used and the respective hand. The accuracy should be calculated based on the text displayed in the sample screen and the text the user types in.

5.3 Sentence drills

Provide sentences to explore formatting

Sentence drills should provide training to the user to explore the formatting of text in various contexts. All the aid that is to be provided for the course has to be provided for the sentence drills too.

5.4 Paragraph drills

Provide training for full length paragraphs

Reload Paragraphs

Paragraph drills should train the user for a full length paragraph without providing any help. Here comes the real test, the user’s typing skill can be tested here because the aids are not provided. Since it is the first challenge to be placed by the user, the system should provide a provision to reload the existing paragraph or move to the previous paragraph until he is satisfied with his performance.

17

5.5 Free drills

Get the text to be practiced from the user

Free drills should facilitate the user to train him for any text he desires. This process can be terminated by the user based on his satisfaction. All the aids that are to be provided for other features should be provided here too.

5.6 Game

Get the type of game

Option to select the speed

Game should allow the user to check his typing skills learnt so far. And should allow the user to select the type of game he needs to play based on his comfort and the speed in which the game is to be played based on his skill.

6. Constraints

Usage of backspace key is strictly prohibited.

7. Quality Ranges

This section defines the quality ranges for performance, robustness, fault tolerance, usability, and similar characteristics for the Keyboard Typing Tutor.

Usability: The System shall be easy-to-use and shall be appropriate for the people who wish to train them in fingering.

8. Other Product Requirements

8.1 System Requirements

The software can run in any windows operating system. The software that should be available for this application are Visual Basic and

Microsoft Access.

9. Documentation Requirements

9.1 User Manual

The User Manual shall describe use of the System from any lay man’s perspective. The User Manual shall include:

← Minimum System Requirements ← All System Features

The User Manual page dimensions shall be in A4 size. The User Manual shall be available as hardcopy.

18


(For the exercise/experiment, prepare a list of all possible questions (with

answers) that are likely to be asked in the viva-voce of the final lab examination.)


2. Prepare Vision document for your project with all necessary detail

using requisite pro.

19


LABORATORY MANUAL




Title of the exercise/experiment : Use case document.

______________________________________________________________



To prepare a use case document for the project using rational

requisitepro.

STEP 2: ACQUISITION






60

2 TURBO C 60



20

1 Open the Rational Requisite pro by selecting

Start ProgramsRational SoftwareRational

requisite pro.

2 Select File New Project and enter project

name and location.

3 Right click the use case document in the left

pane.

4 Select NewDocument Enter document

name.

5 Repeat steps 3 and 4 for each use case

document to be created.

6 Double click the newly created use case

document.

7 Edit the template based on the project and add

requirements.

8 Save the requirements.

d) Calculations

Not applicable.

e) Inference and analysis:(Sample usecase for the project Keyboard typing

tutor).

Keyboard Typing TutorKUMARAGURUCourse

Version 1.0

21

Revision HistoryDate Version Description Author

15/07/2009 1.0 Initial Release D.Sumitha

K.Prabhavathi

Table of Contents

1. Course 1

1.1 Brief Description 1

2. Flow of Events 1

2.1 Basic Flow 1

3. Special Requirements 1

4. Preconditions 1

5. Post Conditions 1

6. Extension Points 1

22

KUMARAGURUCourse Course

Brief Description

This use case allows the actor to train him with the basic characters and its combinations. The actors starting this use case are the students and other users who wish to learn typing.

Flow of Events

The use case begins when the actor selects the “course” option.

Basic Flow

Enter the text

1. The system displays a blank space to enter the text corresponding to the text displayed.

2. The system provides visual aid by highlighting the key to be pressed and the finger to be used.

3. The system checks the text displayed and the text typed.

4. The accuracy calculated is displayed.

Alternative Flows

If the actor chooses to return to main menu, the system should display the menu.

Special Requirements

Nil

Preconditions

Login Before this use case begins the Actor should have logged in to the system.

Post Conditions

There is no post conditions associated with this use case.

Extension Points

There is no extension point associated with this use case.



1.Prepare a use case document for your project using Rational

RequisitePro.

KUMARAGURU23

COLLEGE OF TECHNOLOGY

LABORATORY MANUAL



Course / Branch : MCA

Title of the exercise/experiment : Requirement Management plan.

______________________________________________________________


f) OBJECTIVE OF THE EXERCISE/EXPERIMENT

To prepare the requirement management plan for the given project using

rational requisite pro.

STEP 2: ACQUISITION


g) Facilities/material required to do the exercise/experiment:




60

2 TURBO C 60

a) Procedure for doing the exercise/experiment:


1 Requirement management plan document sets

out guidelines for establishing the requirements

documents, types attributes and traceability to

24

manage project requirements.

2 Open the Rational Requisite pro by selecting

StartProgramRational Software Rational

Requisite pro.

3 Select FileNew Project and enter project name

and location.

4 Double click the requirement management plan

in the left pane.

5 Edit the template based on the project.

6 Save the document.

Note:



b) Calculations

Not applicable.

c) Inference and analysis:(Sample RMP for the project Keyboard typing

tutor).

Keyboard Typing TutorKUMARAGURU

Version 1.0

25

Revision HistoryDate Version Description Author

08/07/2009 1.0 Initial Release D.Sumitha

K.Prabhavathi

26

Table of Contents

1. Introduction 4

1.1 Purpose 41.2 Scope 41.3 Definitions, Acronyms, and Abbreviations 41.4 References 41.5 Overview 4

2. Requirements Management 4

2.1 Organization, Responsibilities, and Interfaces 42.1.1 Customer 42.1.2 User 42.1.3 Stakeholder42.1.4 Project Guide 42.1.5 Project Coordinator 42.2 Contact Table 42.3 Tools, Environment, and Infrastructure 5

3. Requirements Artifacts 5

3.1 Artifact Description 53.1.1 Document Types 53.1.2 Requirement Types 63.2 Traceability 63.2.1 Traceability Criteria for Requirement Types 63.3 Reports and Measures 7

4. Milestones 8

4.1 Inception 84.1.1 Evaluation Criteria 84.1.2 Artifacts 84.2 Elaboration 94.2.1 Evaluation Criteria 94.2.2 Artifacts 94.3 Construction 104.3.1 Artifacts 104.4 Transition 124.4.1 Evaluation Criteria 124.4.2 Artifacts 12

5. Training and Resources 13

27

KUMARAGURU10. Introduction

10.1 Purpose

The purpose of this plan is to establish and document a systematic approach for eliciting, organizing, and documenting the requirements of the system. This plan also establishes and maintains agreement between the customer and the project team on the changing requirements of the system.

10.2 Scope

This plan provides guidelines for the management of Keyboard Typing Tutor.

10.3 Definitions, Acronyms, and Abbreviations

For common vocabulary for this project, please refer to the Glossary document.

10.4 References

Rational Unified Process®, Version 2003 Copyright © 1987 – 2003. Rational Software Corporation

10.5 Overview

This document contains specific details and strategies for managing the requirements of the Keyboard Typing Tutor. The document details how requirements are organized and administrated within our project.

It specifies milestones to be reached and standards to be adhered to so that we can ensure and evaluate fulfillment of the requirements we specify.

11. Requirements Management

11.1 Organization, Responsibilities, and Interfaces

11.1.1 User

A person who will use the system that is developed.

11.1.2 Stakeholder

An individual or organization that is materially affected by the outcome of the system.

11.1.3 Project Guide

The role with overall responsibility for the project. The Project Guide needs to ensure tasks are scheduled, allocated and completed in accordance with project schedules, budgets and quality requirements.

11.1.4 Project coordinator

The Project Coordinator is responsible for ensuring that project standards are correctly and verifiably followed by all project staff.

11.2 Contact Table

Role Name Organization Contact

User Students KCT 0422-2669401

Stakeholder Students KCT 0422-2669401

Project Guide Ms. R.Vanitha KCT 0422-2669401

Project coordinator Mr.S.Hameed Ibrahim KCT 0422-2669401

11.3 Tools, Environment, and Infrastructure

Tool Description License Info

Technical Support

Website

Rational RequisitePro

For managing requirements.

www.rational.com

28

Rational purify For identifying memory leaks and usage

www.rational.com

Rational Test Manager

To create test hierarchy and to do functional testing and performance testing

www.rational.com

Rational Test factory

To analyze code coverage information

www.rational.com

Rational Manual Test

To do manual testing www.rational.com

Rational Pure Coverage

To pin point areas of code that have not been tested

www.rational.com

Rational Robot To perform load testing www.rational.com

Rational SoDA For automated documentation www.rational.com

Rational Quantify To pin point performance bottlenecks

www.rational.com

12. Requirements Artifacts

12.1 Artifact Description

12.1.1 Document Types

Document Type Description Default Requirement Type

Vision (VIS) Conditions or capabilities of this release of the system

Feature (FEAT)

Use-Case Specification (UCS)

Use case description and elaboration. Use Case (UC)

Glossary (GLS) Used to capture common vocabulary. Glossary Item (TERM)

Requirements Management Plan (RMP)

This document type describes requirements and strategies specific to the management and development of the project.

Default for documents without requirements (NONE)

12.1.2 Requirement Types

Requirement Type Description Attributes

Feature (FEAT) An externally observable service provided by the system, which directly fulfills a stakeholder need.

Priority, Type, Status, Difficulty, Stability, Risk, Planned Iteration, Actual Iteration, Origin, Contact

29

Name, Enhancement Request, Defect, Obsolete

Use Case (UC) A description of system behavior, in terms of sequences of actions. A use case should yield an observable result of value to an actor.

Property, Priority, Status, Difficulty, Stability, Risk, Affects Architecture, Contact Name, Planned Iteration, Actual Iteration, Enhancement Request, Defect, Obsolete

Glossary Item (TERM) A term used in the project’s common vocabulary.

12.2 Traceability

12.2.1 Traceability Criteria for Requirement Types

Requirement Type Guidelines Notes

Feature (FEAT) Every Feature with “Approved” status or greater must trace to one or more Supplementary Requirements.

Glossary Item (TERM) Every Glossary term must have a unique and consistent definition throughout all project documents and artifacts.

Use Case (UC) Each Use case should trace to a feature in the vision document.

12.3 Reports and Measures

For reports and measures on this project, use the Requirement Metrics tool, which is available from the Tool menu. In Requirement Metrics, create reports based on requirement types or saved views and query on the following filters:

Attribute Value:

An Attribute Value filter returns the requirements whose attributes have values that match your criteria. The choices you make depend on the data type of the attribute you select in the Attributes drop-down list.

Stakeholder Request

Feature

Use Case

30

Attribute Value Change:

An Attribute Value Change filter returns the requirements with a changed attribute value that matches your BEFORE and AFTER selections. The choices you make depend on the data type of the attribute you select in the Attributes drop-down list. If several changes have been made to the attribute value, your BEFORE selection must specify the value which immediately preceded the current (AFTER) value. To report any change in an attribute value of the selected requirement type, use the Select All buttons for the BEFORE and AFTER selections.

Base Filter:

The Base filter defines the requirement type for a query. Every query is specific to a single requirement type. When you use a saved RequisitePro view defined in the Views Workplace, the Base filter serves as the first filter for requirements. The Base filter cannot be deleted, and is only changed by selecting a new view from the Choose a Requirement View drop-down list.

Children:

The Children filter returns the requirements that have the number of direct children that matches your selection criteria. You must choose which operator to use and enter at least one numeric value. If you choose the "Between" or "Not Between" operator, you must also enter a second numeric value. The default setting (> 0) reports all requirements of the selected type that have any children.

Parent Change

A Parent Change filter returns the requirements whose parent relationship has changed from your BEFORE selection to your AFTER selection. The selections allow you to report requirements that were changed from or to any parent, no parent, or one or more selected parents which you choose. When reporting changes to selected requirements, if a requirement had several changes of parent assignments, your BEFORE selection must specify the value which immediately preceded the current (AFTER) value.

Requirement Creation:

The Requirement Creation filter returns all requirements of the specified requirement type. Typically, this filter is used with the Time Period option to determine which requirements have been created in a specified time period.

Requirement Text Change:

A Requirement Text Change filter returns the requirements whose text has changed the number of times you specify. The filter allows you to choose comparison operators, such as "equal to" (=), "greater than" (>), etc., when specifying the number of times that the text has changed.

Traceability Change:

A Traceability Change filter returns the requirements that had a trace relationship either removed or added, depending on your selection.

View Descriptions:

Query Name Description Requirement Type

Attributes Attribute Value Range

Features displays all requirements of the Feature Type

FEAT all all

Glossary Terms displays all requirements of the Glossary Term Type

TERM all all

31

Use Case Survey displays all requirements of the Use Case Type

UC all all

Requirements traced to Features

Displays traceability between all requirements to features.

ALL to FEAT traceability matrix

Use Cases traced to Features

displays traceability between Use Cases and Features

UC to FEAT traceability matrix

13. Milestones

13.1 Inception

13.1.1 Evaluation Criteria

Stakeholder concurrence on scope definition and cost/schedule estimates

Agreement that the right set of requirements has been captured and that there is a shared understanding of these requirements.

Agreement that the cost/schedule estimates, priorities, risks, and development process are appropriate.

All risks have been identified and a mitigation strategy exists for each.

The project may be aborted or considerably re-thought if it fails to reach this milestone.

13.1.2 Artifacts

Tasks/Artifacts

Description Start Date End Date

Requirements Management Plan This document sets forth our strategy for managing the project requirements

08/jul/2009

Vision Document This document brings together our business proposal and plan with a dynamic vision of the features we propose to deliver.

Use Cases A series of documents and requirements describing how the system will interact with external entities.

Executable The first iteration should deliver an executable product for

32

testing.

Priority/difficulty All requirements should be assigned a priority and difficulty.

13.2 Elaboration

At the end of the elaboration phase is the second important project milestone. At this point, you examine the detailed system objectives and scope, the choice of architecture, and the resolution of the major risks.


The product Vision and requirements are stable.

The architecture is stable.

The key approaches to be used in test and evaluation are proven.

Test and evaluation of executable prototypes have demonstrated that the major risk elements have been addressed and have been credibly resolved.

The iteration plans for the construction phase are of sufficient detail and fidelity to allow the work to proceed.

The iteration plans for the construction phase are supported by credible estimates.

All stakeholders agree that the current vision can be met if the current plan is executed to develop the complete system, in the context of the current architecture.

Actual resource expenditure versus planned expenditure is acceptable.

The project may be aborted or considerably re-thought if it fails to reach this milestone.

13.2.2 Artifacts

Tasks/Artifacts


Outline the iteration plan, risks, and architectural objectives.

After the previous iteration was assessed and the project scope and risk reevaluated, the evaluation criteria for the architecture are outlined, considering the "architectural risks".

Use-Case Analysis To get a general feeling of the obvious classes needed, the system requirements, the glossary and the use-case view and the team's general domain knowledge to sketch the outline of the subsystems, possibly in a layered fashion have to be considered.

Implementation: Plan the integration.

A system integrator now studies the use cases that are to be implemented, and defines the order in which

33

subsystems should be implemented, and later integrated into an architectural prototype..

13.3 Construction

Evaluation Criteria

The evaluation criteria for the construction phase involve the answers to these questions:

Is this product release stable and mature enough to be deployed in the user community?

Are all the stakeholders ready for the transition into the user community?

Are actual resource expenditures versus planned still acceptable?

Transition may have to be postponed by one release if the project fails to reach this milestone.

13.3.1 Artifacts

Tasks/Artifacts


Implementation: Plan system-level integration.

Integration planning takes into account the order in which functional units are to be put together to form a working/testable configuration. The choice depends on the functionality already implemented, and what aspects of the system need to be in place to support the overall integration and test strategy.

Analysis & Design: Refine Use-Case Realizations.

Designers refine the model elements identified in previous iterations by allocating responsibilities to specific model elements (classes or subsystems) and updating their relationships and attributes. New elements may also need to be added to support possible design and implementation constraints. Results of the analysis need to be followed by review(s).

Test: Define Evaluation Mission

The tester gains agreement with stakeholders on the test objectives for this iteration and defines the details of the approach - what will be

34

tested and how.

Implementation: Develop Code and Test Unit

Implementers develop code, in accordance with the project's programming guidelines and they fix defects and provide any feedback that may lead to design changes based on discoveries made in implementation.

Implementation: Plan and Implement Unit Tests.

The implementer needs to design unit tests so that they address what the unit does (black-box), and how it does (white-box). Under black-box (specification) testing the implementer needs to be sure that the unit, in its various states, performs to its specification, and can correctly accept and produce a range of valid and invalid data. Under white-box (structure) testing the challenge for the implementer is to ensure that the design has been correctly implemented, and that the unit can be successfully traversed through each of its decision paths.

Implementation: Test Unit within Subsystem.

Unit Test focuses on verifying the smallest testable components of the software. Unit tests are designed, implemented, and executed by the implementer of the unit.

Implementation: Integrate System.

The purpose of system integration is to combine the currently available implementation model functionality into a build. The system integrator incrementally adds subsystems, and creates a build that is handed over to testers for overall integration testing.

35

13.4 Transition


The primary evaluation criteria for the transition phase involve the answers to these questions:

Is the user satisfied?

Are actual resources expenditures versus planned expenditures acceptable?

At the Product Release Milestone, the product is in production and the post-release maintenance cycle begins. This may involve starting a new cycle, or some additional maintenance release.

13.4.2 Artifacts

Tasks/Artifacts


Project Management

The delivery of reliable software, with acceptable performance and complete functionality. Change Requests (mainly defects and feedback from beta testing) are the input for continuing development. Based on the number and severity of the Change Requests, risk management activities should be invoked.

The production of end-user support and installation material, and the formal aspects of acceptance test has to be planned.

Implementation The planning for implementation is driven by the feedback from beta test and other Change Requests raised during test by the project itself. As defects are fixed and subsystems mature, they are integrated into builds for testing. In transition, the main work is in fixing defects in components, not adding new components. Unit testing is still required, but the purpose in transition is to verify changes and avoid regression, not complete functional verification.

Deployment Deployment Planning at this stage in transition is concerned with establishing the schedule and resources for development of end-user support material, acceptance testing, and production, packaging and distribution of software deployment units.

36

Configuration Management

The configuration management activities continue in parallel with the remaining implementation and test with increasing emphasis on the formality of change control.

All requests for change will require sanction by project coordinator.

Finally, as part of acceptance, it is usually necessary to do a Functional Configuration Audit (FCA) and a Physical Configuration Audit (PCA).

14. Training and Resources

Online materials Rational user manuals Tutorials and training sessions Text under reference books

TEP 3: PRACTICE/TESTING


3. Setup your project with appropriate Requirements Management

Plan template.

4. Prepare Software Requirements Specification(SRS) document for your

project.

37


LABORATORY MANUAL




Title of the exercise/experiment : Use case diagram.

______________________________________________________________


h) OBJECTIVE OF THE EXERCISE/EXPERIMENT

To develop a use case diagram for the project using Rational rose.

Use case diagram present a high level view of how the system is used as

viewed from actors perspective.

A use case diagram contain 1)Actor – things outside the system. Use

cases system-boundaries identifying what the system should do.

Interaction and relationship between actors and use cases in the system

including the associations , decencies and generations.

STEP 2: ACQUISITION


d) Facilities/material required to do the exercise/experiment:


38



60

2 TURBO C 60

e) Procedure for doing the exercise/experiment:


1 Select Start Programs Rational

softwareRational rose enterprise edition.

2 Select rational unified process from the ‘create

new model dialog box’.

3 Right click the logical view from the tree

structure in the left pane. And select NewUse

case diagram.

4 The toolbar consists of actors, use case,

unidirectional association, generation and

dependency.

5 Use the tools to draw the use case diagram.

Note:

f) Calculations

Not applicable.

g) Inference and analysis:(sample )

39

Use Case Diagrams:

Login

Take up the course

Parctice Sentences

Practice Paragraphs

Practice any text using free drills

Test your skills - Game

Student

Use Case Diagram depicting the overall operations

40

Update the text to be typed

Administrator

Enter the given text

Make use of the visual aid

View the accuracy percentage

Return to the Main Menu

Student

Use Case Diagram depicting the Course Module

41

Update the text to be typed

Administrator

Select the speed of the game

Select the type of the game

Enter the text

Select between play, pause and redo

Check on the time left for each text

View the points and result

Exit

Student

Use Case Diagram depicting the Game Module

42

STEP 3: PRACTICE/TESTING(For the exercise/experiment, prepare a list of all possible questions (with



5. What is use case diagram?

6. Prepare the use case diagram using Rational rose for the your

software.

43


LABORATORY MANUAL




Title of the exercise/experiment : Sequence diagram.

______________________________________________________________


i) OBJECTIVE OF THE EXERCISE/EXPERIMENT

To develop a sequence diagram for the given project using Rational

Rose.

STEP 2: ACQUISITION


h) Facilities/material required to do the exercise/experiment:




60

2 TURBO C 60

44

i) Procedure for doing the exercise/experiment:


1 A sequence diagram is a graphical view of a

scenario that shows the object interaction in a

time based sequence – what happens first, what

happens next.

2 An object has state , behavior and identity. A

message icon represents the communication

between the object indicating an action will

follow. The message icon is a horizontal, solid

arrow connecting the line together.

3 Focus of control (FOC) is an advance notational

technique that enhances sequence diagram. It

shows the period of time during which an object

as performs an action, either directly or through

identifying procedure.

4 Select start Programs Rational Software

Rose Enterprise Edition.

5 Select Rational unified process from the ‘Create

new model dialog box.


structure in the left pane and select New

sequence diagram.

7 The toolbar consists of objects, object message

to self, return message.

8 Use the tools to draw the sequence diagram.

Note:

j) Calculations

Not Applicable.

k) Inference and analysis(sample)

45

Sequence Diagrams:

Student : StudentStudent : StudentSystem : <Process

Name>System : <Process

Name>Drills : <Process

Name>Drills : <Process

Name>Admiinistrator : Administrator

Admiinistrator : Administrator

1. Enter the user Name

2. Check for existing user or accept new user

3. Display the menu

4. Select from the menu

5. Invoke the drill

6. Display the options

7. Select a drill

8. Invoke the appropriate drill

9. Display the interface

10. Update the text

11. Enter the text

12. Check the correctness

13. Calculate accuracy

14. Display the accuracy percentage

15. Return to the Main Menu

16. Exit

Sequence Diagram depicting all the Drill Modules

46

Student : StudentStudent : StudentSystem : <Process

Name>System : <Process

Name>Game : <Process

Name>Game : <Process

Name>Admiinistrator : Administrator


1. Enter the user Name

2. Check for existing user or accept new user

3. Display the menu

4. Select from the ...

5. Invoke the game

6. Display the options

7. Select the type and speed of the game

10. Update the text

11. Enter the text

12. Check the correctness

13. Calculate accuracy

14. Display the points and result

8. Invoke the game based on the specified opt...

9. Display the interface

15. Exit

Sequence Diagram depicting all Game Module

47



7. What is sequence diagram?

8. Develop sequence diagram for your project using Rational Rose.


LABORATORY MANUAL




Title of the exercise/experiment : Collaboration diagram

______________________________________________________________


j) OBJECTIVE OF THE EXERCISE/EXPERIMENT

To develop a collaboration diagram for the project.

STEP 2: ACQUISITION


l) Facilities/material required to do the exercise/experiment:




60

2 TURBO C 60

48

m) Procedure for doing the exercise/experiment:


1 Collaboration diagram is an interaction diagram

that’s shows the order of message that

implement an operation or transaction.

2 An object has a state, behavior and identity.

3 Message represent the communication between

messages.

4 Select startProgramsRational software

Rational rose Enterprise Edition.


structure in the left pane. Select New

Collaboration diagrams.

6 The toolbar consists of object, class interface,

object link, link message.

7 Use the tool to draw collaboration diagram.

Note:



n) Calculations

Not applicable.

o) Inference and analysis:

49

Student : Student

System : <Process Name>

Drills : <Process Name>


1: 1. Enter the user Name

4: 4. Select from the menu

15: 15. Return to the Main Menu

2: 2. Check for existing user or accept new user

3: 3. Display the menu

16: 16. Exit

5: 5. Invoke the drill

8: 8. Invoke the appropriate drill

12: 12. Check the correctness

13: 13. Calculate accuracy

6: 6. Display the options

9: 9. Display the interface

14: 14. Display the accuracy percentage

7: 7. Select a drill

11: 11. Enter the text

10: 10. Update the text



9. Prepare a collaboration diagram for your project using Rational

rose.

50


LABORATORY MANUAL




Title of the exercise/experiment : Activity diagram.

______________________________________________________________


k) OBJECTIVE OF THE EXERCISE/EXPERIMENT

To develop activity diagram for the project.

STEP 2: ACQUISITION


p) Facilities/material required to do the exercise/experiment:




60

2 TURBO C 60

q) Procedure for doing the exercise/experiment:


1 Activity represents the performance of the task

51

or duty in a work flow.

2 It represent specific location where the

workflow may branch based upon guard

conditions.

3 Select StartProgramsRational Software

Rational rose enterprise edition

4 Select Rational unified process ‘Create New

Model Dialog Box’

5 Right click the logical view and select

NewActivity diagram.

6 The tool bar consists of state, activity, start

state, end state, state transition, transition to

self, horizontal synchronization, decision.

7 Use the tool to draw the activity diagram.

Note:



r) Calculations

Not applicable.

s) Inference and analysis:(Sample).

52

Enter User Name

Look f or Existing User

Accept New User

Display Menu

Select f rom the menu

Check the choice

Drill Games

Select a Drill

Course Sentence Drill Paragraph Drill Free Drill

Enter the text Enter the Sentences

Enter the Paragraph

Enter the text to be practiced

Calculate the Accuracy

Display the accuracy Percantage

Select the ty pe and speed of the game

Inv oke the timer

Enter the text

Exit

Return to Main Menu

New User

Existing User

53



10. What is activity diagram.

11.Define activity.

12.Draw an activity diagram for your project using Rational rose.

54


LABORATORY MANUAL




Title of the exercise/experiment : Rational purify.

______________________________________________________________


l) OBJECTIVE OF THE EXERCISE/EXPERIMENT

To run the application using rational purify and collect the summary of

error and leak data.

STEP 2: ACQUISITION


m) Facilities/material required to do the exercise/experiment:




60

2 TURBO C 60

n) Procedure for doing the exercise/experiment:


1 Select StartProgramsRational Software

55

Rational purify.

2 Select FileRun in the program name select the

.exe file.

3 In collect frame click error and leak data and

click run.

4 The output of the error and memory leaks are

displayed.

5 Repeat steps 2 and 3 for coverage, error and

leak data in the collect frame.

6 The errors and memory allocations are

displayed.

Note:



o) Calculations

Not applicable.

p) Inference and analysis:

56

Error and Leak Data

Coverage, Error and Leak Data





1. Run your application using Rational Purify and collect coverage, error & leak

data. Create suitable filter settings & extract the report.

Output: a) Summary of memory leaks & memory usage,

b) Processing time and c) Displayed errors, warnings and

bytes leaked.

57


LABORATORY MANUAL




Title of the exercise/experiment : Rational quantify.

______________________________________________________________


q) OBJECTIVE OF THE EXERCISE/EXPERIMENT

To collect , analyze and compare the performance the project.

Rational quantify is a run time analysis tool offers software developers and

testers a practical solution for identifying bottlenecks and then reducing or

eliminating them through systematic engineering,

STEP 2: ACQUISITION


t) Facilities/material required to do the exercise/experiment:




60

58

2 TURBO C 60

u) Procedure for doing the exercise/experiment:


1 Select StartProgramRational software

Rational quantify.

2 Click FileRun. In the run program dialog box ,

select the .exe file.

3 Click run. A call graph indicating the most

expensive path and functioning in the models

are displayed.

4 The function details button can be clicked which

displays the percentage of fours, callers and

descendants for functions.

5 Click on the function list icon in the toolbars to

display the function calls and time.

Note:



v) Calculations

Formulae used with explanations

Sample calculations

w) Inference and analysis:

59

Run Summary

60

Call Graph

Function Detail

Function List

61



13. Using Rational Quantify, collect, analyze and compare the

performance data for your project.

62


LABORATORY MANUAL




Title of the exercise/experiment : Rational Robot.

______________________________________________________________


r) OBJECTIVE OF THE EXERCISE/EXPERIMENT

To record and playback the test script using Rational Robot for performance.

Rational Robot can be used to develop two kind of scripts.

1.GuI scripts for function testing

2.Vu and VB script for performance testing.

Rational Robot used to:

Perform full function testing.

Perform full performance testing.

STEP 2: ACQUISITION


x) Facilities/material required to do the exercise/experiment:


1 P IV 3.0 GHZ 2GB DDR 60

63


2 TURBO C 60

y) Procedure for doing the exercise/experiment:


1 Select StartProgramsRational Robot

2 Select GUI script and enter name for it.

3 A GUI record dialog box appears with options

and choose project.

4 Select the stop button in GUI record dialog box

after completion.

5 The script is generated

6 Select playback button and give a name in the

playback dialog box

7 Give the build name.

8 Rational robot starts playing back the entire

process.

9 Report is generated with pass and fail indication

of each function.

Note:



z) Calculations

Not applicable.

aa) Inference and analysis:

64

Create a GUI Script

Record GUI Script

65

Status Report

Robot Script



14. Record and play back the test script using Rational Robot for

performance testing.

66


LABORATORY MANUAL




Title of the exercise/experiment : Rational Test Factory.

______________________________________________________________


s) OBJECTIVE OF THE EXERCISE/EXPERIMENT

To run the application, instrument, map and pilot it using Rational Test

factory and collect, code coverage information and mapping summary.

STEP 2: ACQUISITION


bb) Facilities/material required to do the exercise/experiment:




60

2 TURBO C 60

cc) Procedure for doing the exercise/experiment:

67


1 Start program Rational softwareRational

Test factory.

2 Select the user and Rational Project

3 New project wizard dialog box opens, select the

executable and programming language.

4 Select tools Instrument. Add the project files

and the path to rebuild.

5 Click on the “Instrument button” the project will

run, and the instrumentation and rebuild will be

completed.

6 SelectToolsApplication ManagerAut

executable, select the depth as single level and

click finish.

7 A mapping summary will be generated

8 The script will run and report on code coverage

will be generated

Note:



dd) Calculations

Not applicable.

ee) Inference and analysis:

68

Instrument

69

Application Manager

STEP 3: PRACTICE/TESTING(For the exercise/experiment, prepare a list of all possible questions (with



15. Instrument, map and pilot run your application under test (AUT) using

Rational Test Factory. Collect a) Code coverage information and b)

Mapping summary.

16.What is test factory?

17.What is auto pilot?

70


LABORATORY MANUAL




Title of the exercise/experiment : Rational Test manager.

______________________________________________________________


t) OBJECTIVE OF THE EXERCISE/EXPERIMENT

To develop test case hierarchy , specify test preconditions , post conditions with

acceptance criteria using Rational Test manager.

STEP 2: ACQUISITION


ff) Facilities/material required to do the exercise/experiment:




60

2 TURBO C 60

gg) Procedure for doing the exercise/experiment:


1 Click Start ProgramsRational

softwareRational Test manager.

71

2 Select the user and the rational project.

3 Select the File New Test planEnter name

and description and click ok

4 In the new dialog box opened for the test plan,

right click the test plan and Insert test case

folder and Enter n name and click ok

5 Right click the new test case folder and insert

test case.

6 Enter the name and description, click on the

Implementation Tab and under Automated

implementation, click SelectGUI Select a

test script and click ok. Give the precondition,

post condition and acceptance criteria.

7 Right click the test case and select run.

8 The script will run and the test case results will

be displayed.

9 Select the analysis tab on the left pane

10 Expand the listing reports

11 Select the reports for the following listings

Build, log, script, user, test plan and click run to

generate the reports.

Note:



hh) Calculations

Not applicable.

ii) Inference and analysis:

72

Test Case Execution

Test Case Results

73

Build Listing

Log Listing

74

Script Listing

User Listing

75

Test Plan Listing





18. What is test manager?

19.Record and play back the test script using Rational Robot for

performance testing. Use Rational Test Manager to review and analyze

test log details.s

76

software project management lab manual

Documents