Software Project Management Lab Manual

KUMARAGURU
COLLEGE OF TECHNOLOGY
COIMBATORE-641006
SOFTWARE DEVELOPMENT LAB
--------------------------------------------------
LABORATORY MANUAL
DEPARTMENT OF MCA
1
CONTENTS Exercise no.

I II III IV V VI VII VIII IX X XI XII XIII
Title of the Exercise

Rational Administrator Vision Document Use Case Document Requirement Management Plan Use Case Diagram Sequence Diagram Collaboration Diagram Activity Diagram Rational Purify Rational Quantify Rational Robot Rational Test Factory Rational Test Manager
Page no.
3 11 20 24 38 43 47 50 54 57 62 66 70
KUMARAGURU
LABORATORY MANUAL Exercise/Experiment Number: 1

Lab Code / Lab Course / Branch : : Software development lab MCA.
Rational Administrator
Title of the exercise/experiment :
______________________________________________________________
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. 1 2 Facilities/material required Quantity P IV 3.0 GHZ 2GB DDR 60 RAM 80 GB HDD MACHINE TURBO C 60
c)
Procedure for doing the exercise/experiment: Steps 1 Description (in full) Open Rational administrator by clicking start Programs 2 3 4 Rational software Rational administrator. Select File new Project and enter the project name and location. Enter the password with which we can connect to, configure or delete the project. Read the summary of the project settings provided and configure the project and click the
5 6 7 8 9
finish button. If the configure project now option is selected , the configure project dialog box opens. Create an associated requisitepro project with the required template. Create an associated Test Data source- choose the type of data store. Right click and select the connect option on the project name. Create test group by right clicking test group (in tree structure) and selecting the Insert Test Group option. Name the test group and set it as default group and edit the privilege based on the need. Create a Test user by right cliking test user(in the tree structure) and selecting the insert test user option. Enter the user ID and other necessary details. And click ok, the test user is created.
10 11
12 Note: d) Calculations Not applicable. e)
Inference and analysis:
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
KUMARAGURU

Lab Code / Lab Course / Branch : : P07CA504 Software development lab. MCA.
Vision Document.
______________________________________________________________
a) OBJECTIVE OF THE EXERCISE/EXPERIMENT To prepare a vision document for a project using Rational requisite pro.
STEP 2: ACQUISITION
b) Facilities/material required to do the exercise/experiment: Sl.No. 1 2 Facilities/material required Quantity P IV 3.0 GHZ 2GB DDR 60 RAM 80 GB HDD MACHINE TURBO C 60
c) Procedure for doing the exercise/experiment: Steps 1 Description (in full) Open Rational Requisitepro by clicking Start ProgramsRational Requisite pro, Software Rational
10
2 3 4 5 6 7 Note:
Select FileNew Project and enter the project name and location. Right click the Features and vision document in the left pane. Select NewDocument Enter document name Double click the newly created vision document. Edit the template based on the project and add requirements. Save the document.
(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 Tutor

KUMARAGURU Version 1.0
11
Revision History
Date 10/07/2009 Version 1.0 Description Initial Release Author N.Jayakanthan
12
Table of Contents
1. Introduction 1.1 Purpose 1.2 Scope 1.3 Definitions, Acronyms and Abbreviations 1.4 References 2. Positioning 2.1 Business Opportunity 2.2 Problem Statement 2.3 Product Position Statement 3. Stakeholder and User Descriptions 3.1 Stakeholder Summary 3.2 User Summary 3.3 Key Stakeholder / User Needs 4. Product Overview 4.1 Summary of Capabilities 5. Product Features 5.1 Login 5.2 Course 6. Constraints 7. Quality Ranges 8. Other Product Requirements 8.1 System Requirements 9. Documentation Requirements 9.1 User Manual Course Brief Description Flow of Events Basic Flow 15 15 15 15 15 15 15 15 16 16 16 16 16 17 17 17 17 17 18 18 18 18 18 18 25 25 25 25
Enter the text ........................................................................................................................25

1. The system displays a blank space to enter the text corresponding to the text displayed. 3. The system checks the text displayed and the text typed. 4. The accuracy calculated is displayed. Alternative Flows Special Requirements 25 25 25 25 25
13
Preconditions Post Conditions Extension Points 10. Introduction 10.1 Purpose 10.2 Scope 10.3 Definitions, Acronyms, and Abbreviations 10.4 References 10.5 Overview 11. Requirements Management 11.1 Organization, Responsibilities, and Interfaces
25 25 25 31 31 31 31 31 31 31 31
11.1.1 User.............................................................................................................................31 11.1.2 Stakeholder ................................................................................................................31 11.1.3 Project Guide .............................................................................................................31 11.1.4 Project coordinator .....................................................................................................31
11.2 Contact Table 11.3 Tools, Environment, and Infrastructure 12. Requirements Artifacts 12.1 Artifact Description 31 31 32 32
12.1.1 Document Types.........................................................................................................32 12.1.2 Requirement Types.....................................................................................................32

12.2 Traceability 12.3 Reports and Measures 13. Milestones 13.1 Inception 33 33 35 35
12.2.1 Traceability Criteria for Requirement Types..............................................................33
13.1.1 Evaluation Criteria......................................................................................................35 13.1.2 Artifacts.......................................................................................................................35

13.2 Elaboration 36

13.3 Construction 13.4 Transition 37 38
13.3.1 Artifacts.......................................................................................................................37 13.4.1 Evaluation Criteria......................................................................................................38 13.4.2 Artifacts.......................................................................................................................39

14. Training and Resources 40
14
KUMARAGURU
1. 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
2.
2.1
www.w3school.com www.knowledgeisland.com
Business Opportunity
Positioning 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 affects The impact of which is A successful solution would Problem Statement The manual training process. Students and other users. Time consuming and less efficiency. Calculating the accuracy percentage and speed. The problem of
15
2.3 For Who
Product Position Statement Students Wish to improve their typing speed is a software Enables quick and efficient learning The existing manual training Provides in-built features to keep a check on accuracy and speed
The Keyboard Typing Tutor That Unlike Our product
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 Name Students Stakeholder Summary Role Ensures that their typing skills has improved.
3.2 Name
User Summary Description Learns typing in a quick and more efficient way. Stakeholder Self-represented
Students
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 Quick learning Priority High Concerns Time intensive work Inefficiency Current Solution The students have to take up courses to learn typing. The typing efficiency cannot be effectively measured. Proposed Solutions Computerized system which eases the learning process. Computerized system which calculates the typing efficiency then and there.
Efficiency
High
16
4.
Product Overview
4.1 Summary of Capabilities
Customer Support System Customer Benefit Supporting Features Easy 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 users 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. 7.
Constraints Usage of backspace key is strictly prohibited. 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 mans perspective. The User Manual shall include:
o o
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.)
Questions with answers:

2. Prepare Vision document for your project with all necessary detail using requisite pro.
19
KUMARAGURU

Use case document.
______________________________________________________________
a) OBJECTIVE OF THE EXERCISE/EXPERIMENT To prepare a use case document for the project using rational requisitepro.
STEP 2: ACQUISITION
b) Facilities/material required to do the exercise/experiment: Sl.No. 1 2 Facilities/material required Quantity P IV 3.0 GHZ 2GB DDR 60 RAM 80 GB HDD MACHINE TURBO C 60
c) Procedure for doing the exercise/experiment: Steps 1 Description (in full) Open the Rational Requisite pro by selecting Start ProgramsRational SoftwareRational
20
2 3 4 5 6 7
requisite pro. Select File New Project and enter project name and location. Right click the use case document in the left pane. Select NewDocument Enter document
name. Repeat steps 3 and 4 for each use case document to be created. Double click the newly created use case document. Edit the template based on the project and add requirements.
8 d) Calculations
Save the requirements.
Not applicable. e) Inference and analysis:(Sample usecase for the project Keyboard typing tutor).
Keyboard Typing Tutor KUMARAGURUCourse

Version 1.0
21
Revision History
Date 15/07/2009 Version 1.0 Initial Release Description Author D.Sumitha K.Prabhavathi
Table of Contents
1. Introduction 1.1 Purpose 1.2 Scope 1.3 Definitions, Acronyms and Abbreviations 1.4 References 2. Positioning 2.1 Business Opportunity 2.2 Problem Statement 2.3 Product Position Statement 3. Stakeholder and User Descriptions 3.1 Stakeholder Summary 3.2 User Summary 3.3 Key Stakeholder / User Needs 4. Product Overview 4.1 Summary of Capabilities 5. Product Features 5.1 Login 5.2 Course 6. Constraints 7. Quality Ranges 8. Other Product Requirements 8.1 System Requirements 9. Documentation Requirements 9.1 User Manual Course Brief Description Flow of Events 15 15 15 15 15 15 15 15 16 16 16 16 16 17 17 17 17 17 18 18 18 18 18 18 25 25 25
22
Basic Flow
25
Enter the text ........................................................................................................................25

1. The system displays a blank space to enter the text corresponding to the text displayed. 3. The system checks the text displayed and the text typed. 4. The accuracy calculated is displayed. Alternative Flows Special Requirements Preconditions Post Conditions Extension Points 10. Introduction 10.1 Purpose 10.2 Scope 10.3 Definitions, Acronyms, and Abbreviations 10.4 References 10.5 Overview 11. Requirements Management 11.1 Organization, Responsibilities, and Interfaces 25 25 25 25 25 25 25 25 31 31 31 31 31 31 31 31


13.2 Elaboration 36

13.3 Construction 37
23
13.3.1 Artifacts.......................................................................................................................37
13.4 Transition 38

24
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.
Questions with answers: 1.Prepare a use case document for your project using Rational RequisitePro.
25
KUMARAGURU

Lab Code / Lab Course / Branch : : P07CA504 Software development lab. MCA
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)
a)
Procedure for doing the exercise/experiment: Steps 1 Description (in full) Requirement management plan document sets out guidelines for establishing the requirements documents, types attributes and traceability to 2 manage project requirements. Open the Rational Requisite pro by selecting 26
StartProgramRational Software Rational 3 4 5 6 Note: Requisite pro. Select FileNew Project and enter project name and location. Double click the requirement management plan in the left pane. Edit the template based on the project. Save the document.
(Diagrams like circuit diagrams, chart like process charts and so on are to be provide as per the requirement of the exercise.) b) c) Calculations Not applicable. Inference and analysis:(Sample RMP for the project Keyboard typing tutor).
Keyboard Typing Tutor KUMARAGURU

Version 1.0
27
Revision History
Date 08/07/2009 Version 1.0 Description Initial Release Author D.Sumitha K.Prabhavathi
28
Table of Contents
1. Introduction 1.1 Purpose 1.2 Scope 1.3 Definitions, Acronyms and Abbreviations 1.4 References 2. Positioning 2.1 Business Opportunity 2.2 Problem Statement 2.3 Product Position Statement 3. Stakeholder and User Descriptions 3.1 Stakeholder Summary 3.2 User Summary 3.3 Key Stakeholder / User Needs 4. Product Overview 4.1 Summary of Capabilities 5. Product Features 5.1 Login 5.2 Course 6. Constraints 7. Quality Ranges 8. Other Product Requirements 8.1 System Requirements 9. Documentation Requirements 9.1 User Manual Course Brief Description Flow of Events Basic Flow 15 15 15 15 15 15 15 15 16 16 16 16 16 17 17 17 17 17 18 18 18 18 18 18 25 25 25 25
Enter the text ........................................................................................................................25

1. The system displays a blank space to enter the text corresponding to the text displayed. 3. The system checks the text displayed and the text typed. 4. The accuracy calculated is displayed. Alternative Flows Special Requirements Preconditions Post Conditions 25 25 25 25 25 25 25
29
Extension Points 10. Introduction 10.1 Purpose 10.2 Scope 10.3 Definitions, Acronyms, and Abbreviations 10.4 References 10.5 Overview 11. Requirements Management 11.1 Organization, Responsibilities, and Interfaces
25 31 31 31 31 31 31 31 31


13.2 Elaboration 36

13.3 Construction 13.4 Transition 37 38
13.3.1 Artifacts.......................................................................................................................37 13.4.1 Evaluation Criteria......................................................................................................38 13.4.2 Artifacts.......................................................................................................................39

30
KUMARAGURU
10. 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 Role User Stakeholder Project Guide Project coordinator 11.3 Tool Rational RequisitePro Rational purify Contact Table Name Students Students Ms. R.Vanitha Mr.S.Hameed Ibrahim Organization KCT KCT KCT KCT Contact 0422-2669401 0422-2669401 0422-2669401 0422-2669401
Tools, Environment, and Infrastructure Description For managing requirements. For identifying memory leaks and usage License Info Technical Support Website www.rational.com www.rational.com
31
Rational Test Manager
To create test hierarchy and to do functional testing and performance testing To analyze code coverage information To do manual testing
www.rational.com
Rational Test factory Rational Manual Test Rational Pure Coverage
www.rational.com
www.rational.com www.rational.com
To pin point areas of code that have not been tested

To perform load testing For automated documentation
Rational Robot Rational SoDA Rational Quantify
www.rational.com www.rational.com www.rational.com
To pin point performance bottlenecks
12.
Requirements Artifacts
12.1 Artifact Description 12.1.1 Document Types
Document Type
Vision (VIS) Use-Case Specification (UCS) Glossary (GLS) Requirements Management (RMP) Plan
Description
Conditions or capabilities of this release of the system Use case description and elaboration. Used to capture common vocabulary. This document type describes requirements and strategies specific to the management and development of the project.
Default Requirement Type

Feature (FEAT) Use Case (UC) Glossary Item (TERM) Default for documents requirements (NONE) without
12.1.2 Requirement Types
Requirement Type
Feature (FEAT)
Description
An externally observable service provided by the system, which directly fulfills a stakeholder need.
Attributes
Priority, Type, Status, Difficulty, Stability, Risk, Planned Iteration, Actual Iteration, Origin, Contact Name, Enhancement Request, Defect, Obsolete Property, Priority, Status, Difficulty, Stability, Risk, Affects Architecture, Contact Name, Planned Iteration,
Use Case (UC)
A description of system behavior, in terms of sequences of actions. A use case should yield an observable
32
result of value to an actor. Glossary Item (TERM) A term used in the projects common vocabulary.
Actual Iteration, Enhancement Request, Defect, Obsolete
12.2
Traceability
Stakeholder Request
Feature
Use Case
12.2.1 Traceability Criteria for Requirement Types
Requirement Type
Feature (FEAT)
Guidelines
Every Feature with Approved status or greater must trace to one or more Supplementary Requirements. Every Glossary term must have a unique and consistent definition throughout all project documents and artifacts.
Notes
Glossary Item (TERM)
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. Attribute Value Change:
33
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 Features Description displays all requirements of the Feature Type displays all requirements of the Glossary Term Type Requirement Type FEAT Attributes all Attribute Range all Value
Glossary Terms
TERM
all
all
34
Use Case Survey
displays all requirements of the Use Case Type Displays traceability between all requirements to features. displays traceability between Use Cases and Features
UC
all
all
Requirements traced to Features
ALL to FEAT
traceability matrix
Use Cases traced to 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 08/jul/2009 forth our strategy for managing the project requirements This document brings together our business proposal and plan with a dynamic vision of the features we propose to deliver. A series of documents and requirements describing how the system will interact with external entities. The first iteration should deliver an executable product for testing.
Vision Document
Use Cases
Executable
35
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. 13.2.1 Evaluation Criteria 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 Description Start Date End Date
Outline the iteration plan, After the previous iteration risks, and architectural was assessed and the project objectives.
scope and risk reevaluated, the evaluation criteria for the architecture are outlined, considering the "architectural risks".
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.
Use-Case Analysis
Implementation: Plan the integration.
A system integrator now studies the use cases that are to be implemented, and defines the order in which subsystems should be implemented, and later integrated into an architectural prototype.. 36
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 Description Start Date End Date
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 Designers refine the model Use-Case Realizations. 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 The tester gains agreement Mission with stakeholders on the test objectives for this iteration and defines the details of the approach - what will be tested and how. Implementation: Develop Implementers develop code, Code and Test Unit in accordance with the project's programming guidelines and they fix defects and provide any 37
feedback that may lead to design changes based on discoveries made in implementation. Implementation: Plan and The implementer needs to Implement Unit Tests. design unit tests so that they address what the unit does (black-box), and how it does (white-box). Under blackbox (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 Test focuses on Unit within Subsystem. verifying the smallest testable components of the software. Unit tests are designed, implemented, and executed by the implementer of the unit. Implementation: IntegrateThe purpose of system 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.
13.4 Transition
13.4.1 Evaluation Criteria 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?
38
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 Description Start Date End Date
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. 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 Planning at this stage in transition is concerned with establishing the schedule and resources for development of enduser support material, acceptance testing, and production, packaging and distribution of software deployment units. 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).
Implementation
Deployment
Configuration Management
39
14.
TEP 3: PRACTICE/TESTING
Questions with answers: 3. Setup your project with appropriate Requirements Management Plan template.
4. Prepare Software Requirements Specification(SRS) document for your project.
Training and Resources Online materials Rational user manuals Tutorials and training sessions Text under reference books
KUMARAGURU
LABORATORY MANUAL
40
Exercise/Experiment Number: 5
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)
e)
Procedure for doing the exercise/experiment: Steps 1 2 Description (in full) Select Start Programs Rational
softwareRational rose enterprise edition. Select rational unified process from the create 41
new model dialog box. Right click the logical view from the tree structure in the left pane. And select NewUse case diagram. The toolbar consists of actors, use case, unidirectional association, generation and dependency. Use the tools to draw the use case diagram.
5 Note: f) g) Calculations
Not applicable. Inference and analysis:(sample )
Use Case Diagrams:
42
Login
T ake up the course
P arctice S entences
S tudent P ractice P aragraphs
P ractice anytex using free drills t
T y skills - G e est our am
Use Case Diagram depicting the overall operations
Update the text to be typed
Enter the given text
Student Make us e of the visual aid
Adm inistrator
View the accuracy percentage
Return to the Main Menu
Use Case Diagram depicting the Course Module 43
U p d a te th e te xt to b e typ e d
S e le c t th e s p e e d o f th e g a m e
S e le c t th e typ e o f th e g a m e
S tu d e n t
E n te r th e te xt
Ad m in is tra to r
S e le c t b e tw e e n p la y, p a u s e a n d re d o
C h e c k o n th e tim e le ft fo r e a c h te xt
Vie w th e p o in ts a n d re s u lt
E xit
Use Case Diagram depicting the Game Module
44
Questions with answers: 5. What is use case diagram? 6. Prepare the use case diagram using Rational rose for the your software.
45
KUMARAGURU

Sequence diagram.
______________________________________________________________
i) OBJECTIVE OF THE EXERCISE/EXPERIMENT To develop a sequence diagram for the given project using Rational Rose.
STEP 2: ACQUISITION
h)
i)
Procedure for doing the exercise/experiment: Steps 1 Description (in full) A sequence diagram is a graphical view of a scenario that shows the object interaction in a 46
time based sequence what happens first, what 2 happens next. 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 3 arrow connecting the line together. 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 4 5 identifying procedure. Select start Programs Rational Software Rose Enterprise Edition. Select Rational unified process from the Create new model dialog box. 6 Right click the logical view from the tree structure in the left pane and select New 7 8 Note: j) k) Calculations Not Applicable. Inference and analysis(sample) sequence diagram. The toolbar consists of objects, object message to self, return message. Use the tools to draw the sequence diagram.
Sequence Diagrams:
47
Student : Student 1. Enter the us er Nam e
Sys tem : <Proces s Nam e>
Drills : <Proces s Nam e>
Adm iinis trator : Adm inis trator
2. Check for exis ting us er or accept new us er 3. Dis play the m enu
4. Select from the m enu
5. Invoke the drill
6. Dis play the options 7. Select a drill 8. Invoke the appropriate drill
9. Dis play the interface
10. Update the text
11. Enter the text 12. Check the correctnes s 13. Calculate accuracy
14. Dis play the accuracy percentage 15. Return to the Main Menu 16. Exit
Sequence Diagram depicting all the Drill Modules
48
Student : Student 1. Enter the us er Nam e
System : <Process Nam e>
Game : <Process Nam e>
Admiinistrator : Adm inistrator
2. Check for exis ting user or accept new user 3. Display the menu
4. Select from the ...
5. Invoke the gam e
6. Dis play the options 7. Select the type and s peed of the game 8. Invoke the gam e bas ed on the s pecified opt...
9. Dis play the interface
10. Update the text
11. Enter the text 12. Check the correctnes s 13. Calculate accuracy
14. Display the points and result 15. Exit
Sequence Diagram depicting all Game Module
49
Questions with answers: 7. What is sequence diagram? 8. Develop sequence diagram for your project using Rational Rose.
KUMARAGURU

Lab Code / Lab Course / Branch : P07CA504 Software development lab. : MCA
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)
m)
Procedure for doing the exercise/experiment: Steps Description (in full) 50
Collaboration diagram is an interaction diagram thats shows the order of message that implement an operation or transaction. An object has a state, behavior and identity. Message represent the communication between messages. Select startProgramsRational software
2 3 4 5
Rational rose Enterprise Edition. Right click the logical view from the tree structure in the left pane. Select New Collaboration diagrams. The toolbar consists of object, class interface, object link, link message. Use the tool to draw collaboration diagram.
6 7 Note:
(Diagrams like circuit diagrams, chart like process charts and so on are to be provide as per the requirement of the exercise.) n) o) Calculations Not applicable. Inference and analysis:
51
1: 1. Enter the us er Nam e 4: 4. Select from the m enu 15: 15. Return to the Main Menu
Sys tem : <Proces s Nam e> 2: 2. Check for exis ting us er or accept new us er Student : Student 3: 3. Dis play the m enu 16: 16. Exit
10: 10. Update the text 13: 13. Calculate accuracy 6: 6. Dis play the options 9: 9. Dis play the interface 14: 14. Dis play the accuracy percentage 5: 5. Invoke the drill 8: 8. Invoke the appropriate drill 12: 12. Check the correctnes s
7: 7. Select a drill 11: 11. Enter the text
Adm iinis trator : Adm inis trator
Drills : <Proces s Nam e>
Questions with answers: 9. Prepare a collaboration diagram for your project using Rational rose.
52
KUMARAGURU

Activity diagram.
______________________________________________________________
k) OBJECTIVE OF THE EXERCISE/EXPERIMENT To develop activity diagram for the project.
STEP 2: ACQUISITION
p)
q)
Procedure for doing the exercise/experiment: Steps 1 2 3 Description (in full) Activity represents the performance of the task or duty in a work flow. It represent specific location where the workflow may branch based upon guard conditions. Select StartProgramsRational Software Rational rose enterprise edition 53
4 5 6
Select Rational unified process Create New Model Dialog Box Right click the logical view and select
NewActivity diagram. The tool bar consists of state, activity, start state, end state, state transition, transition to self, horizontal synchronization, decision. Use the tool to draw the activity diagram.
7 Note:
(Diagrams like circuit diagrams, chart like process charts and so on are to be provide as per the requirement of the exercise.) r) s) Calculations Not applicable. Inference and analysis:(Sample).
54
Enter User Name
New User Accept New User
Existing User Look f or Existing User
Display Menu
Select f rom the menu Check the choice
Drill
Games
Select a Drill Select the ty pe and speed of the game
Inv oke the timer Course Sentence Drill Paragraph Drill Free Drill
Enter the text
Enter the Sentences
Enter the Paragraph
Enter the text to be practiced
Enter the text
Calculate the Accuracy
Display the accuracy Percantage Return to Main Menu
Exit
55
Questions with answers: 10. What is activity diagram. 11. Define activity. 12. Draw an activity diagram for your project using Rational rose.
56
KUMARAGURU

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)
n)
Procedure for doing the exercise/experiment: Steps 1 2 3 4 Description (in full) Select StartProgramsRational Software Rational purify. Select FileRun in the program name select the .exe file. In collect frame click error and leak data and click run. The output of the error and memory leaks are displayed. 57
5 6 Note:
Repeat steps 2 and 3 for coverage, error and leak data in the collect frame. The errors and memory displayed. allocations are
(Diagrams like circuit diagrams, chart like process charts and so on are to be provide as per the requirement of the exercise.) o) Calculations p) Not applicable.
Error and Leak Data
58
Coverage, Error and Leak Data
Questions with answers: 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 bytes leaked. c) Displayed errors, warnings and
59
KUMARAGURU

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)
u)
Procedure for doing the exercise/experiment: Steps 1 Description (in full) Select StartProgramRational software 60
2 3
Rational quantify. Click FileRun. In the run program dialog box , select the .exe file. Click run. A call graph indicating the most expensive path and functioning in the models are displayed. The function details button can be clicked which displays the percentage of fours, callers and descendants for functions. Click on the function list icon in the toolbars to display the function calls and time.
5 Note:
(Diagrams like circuit diagrams, chart like process charts and so on are to be provide as per the requirement of the exercise.) v) Calculations w) Formulae used with explanations Sample calculations
61
Run Summary
Call Graph
Function Detail
62
Function List
Questions with answers: 13. Using Rational Quantify, collect, analyze and compare the
performance data for your project.
63
KUMARAGURU

Lab Code / Lab Course / Branch : P07CA504 Software development lab. : MCA
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
64
2.Vu and VB script for performance testing. Rational Robot used to: Perform full function testing. Perform full performance testing.
STEP 2: ACQUISITION
x)
y)
Procedure for doing the exercise/experiment: Steps 1 2 3 4 5 6 7 8 9 Note: (Diagrams like circuit diagrams, chart like process charts and so on are to be provide as per the requirement of the exercise.) Description (in full) Select StartProgramsRational Robot Select GUI script and enter name for it. A GUI record dialog box appears with options and choose project. Select the stop button in GUI record dialog box after completion. The script is generated Select playback button and give a name in the playback dialog box Give the build name. Rational robot starts playing back the entire process. Report is generated with pass and fail indication of each function.
z)
Calculations Not applicable.
65
aa)
Create a GUI Script
Record GUI Script
66
Status Report
Robot Script
Questions with answers: 14. Record and play back the test script using Rational Robot for
performance testing.
67
KUMARAGURU

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)
cc)
Procedure for doing the exercise/experiment: Steps 1 2 3 Description (in full) Start program Rational softwareRational Test factory. Select the user and Rational Project New project wizard dialog box opens, select the 68
4 5
executable and programming language. Select tools Instrument. Add the project files and the path to rebuild. Click on the Instrument button the project will run, and the instrumentation and rebuild will be completed.
SelectToolsApplication
ManagerAut
executable, select the depth as single level and 7 8 Note: (Diagrams like circuit diagrams, chart like process charts and so on are to be provide as per the requirement of the exercise.) dd) Calculations ee) Not applicable. click finish. A mapping summary will be generated The script will run and report on code coverage will be generated
69
Instrument
70
Application Manager
Questions with answers: 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?
71
KUMARAGURU

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)
gg)
Procedure for doing the exercise/experiment: Steps 1 2 3 4 Description (in full) Click Start ProgramsRational
softwareRational Test manager. Select the user and the rational project. Select the File New Test planEnter name and description and click ok 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 72
5 6
Right click the new test case folder and insert test case. 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. Right click the test case and select run. The script will run and the test case results will be displayed. Select the analysis tab on the left pane Expand the listing reports Select the reports for the following listings Build, log, script, user, test plan and click run to generate the reports.
7 8 9 10 11
Note: (Diagrams like circuit diagrams, chart like process charts and so on are to be provide as per the requirement of the exercise.) hh) Calculations ii) Not applicable.
73
Test Case Execution
Test Case Results
Build Listing
74
Log Listing
Script Listing
75
User Listing
Test Plan Listing
76
Questions with answers: 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
77

Software Project Management Lab Manual

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Software Project Management Lab Manual

Uploaded by

Copyright:

Available Formats

KUMARAGURU

SOFTWARE DEVELOPMENT LAB

CONTENTS Exercise no.

Title of the Exercise

LABORATORY MANUAL Exercise/Experiment Number: 1

Title of the exercise/experiment :

12 Note: d) Calculations Not applicable. e)

Inference and analysis:

1. Note: Furnish suitable descriptions wherever required

LABORATORY MANUAL Exercise/Experiment Number: 2

Title of the exercise/experiment :

Keyboard Typing Tutor

Enter the text ........................................................................................................................25

12.1.1 Document Types.........................................................................................................32 12.1.2 Requirement Types.....................................................................................................32

12.2.1 Traceability Criteria for Requirement Types..............................................................33

13.1.1 Evaluation Criteria......................................................................................................35 13.1.2 Artifacts.......................................................................................................................35

13.2.1 Evaluation Criteria......................................................................................................36 13.2.2 Artifacts.......................................................................................................................36

2.3 For Who

The Keyboard Typing Tutor That Unlike Our product

Stakeholder and User Descriptions

Key Stakeholder / User Needs

Provide effective help

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

Constraints Usage of backspace key is strictly prohibited. Quality Ranges

Other Product Requirements

Minimum System Requirements All System Features

Questions with answers:

LABORATORY MANUAL Exercise/Experiment Number: 3

Title of the exercise/experiment :

Save the requirements.

Keyboard Typing Tutor KUMARAGURUCourse

Enter the text ........................................................................................................................25

12.1.1 Document Types.........................................................................................................32 12.1.2 Requirement Types.....................................................................................................32

12.2.1 Traceability Criteria for Requirement Types..............................................................33

13.1.1 Evaluation Criteria......................................................................................................35 13.1.2 Artifacts.......................................................................................................................35

13.2.1 Evaluation Criteria......................................................................................................36 13.2.2 Artifacts.......................................................................................................................36

13.4.1 Evaluation Criteria......................................................................................................38 13.4.2 Artifacts.......................................................................................................................39

LABORATORY MANUAL Exercise/Experiment Number: 4

Title of the exercise/experiment :

Keyboard Typing Tutor KUMARAGURU

Enter the text ........................................................................................................................25

12.1.1 Document Types.........................................................................................................32 12.1.2 Requirement Types.....................................................................................................32

12.2.1 Traceability Criteria for Requirement Types..............................................................33

13.1.1 Evaluation Criteria......................................................................................................35 13.1.2 Artifacts.......................................................................................................................35

13.2.1 Evaluation Criteria......................................................................................................36 13.2.2 Artifacts.......................................................................................................................36

Rational Test Manager

Rational Test factory Rational Manual Test Rational Pure Coverage

To pin point areas of code that have not been tested

Rational Robot Rational SoDA Rational Quantify

www.rational.com www.rational.com www.rational.com

To pin point performance bottlenecks

Default Requirement Type

12.1.2 Requirement Types

Use Case (UC)

Actual Iteration, Enhancement Request, Defect, Obsolete

Glossary Item (TERM)

Use Case (UC)

Each Use case should trace to a feature in the vision document.

Reports and Measures

Use Case Survey

Requirements traced to Features

Use Cases traced to Features

Requirements Management Plan