ROLL NO – 2028216 SUBJECT CODE : BTCS-506-18

Practical-1
Aim : Study and usage of Open Project or similar software to draft a project plan.
1.1 Introduction of MS Project:
Microsoft Project is a project management software program developed and sold by Microsoft,
designed to assist a project manager in developing a schedule, assigning resources to tasks, tracking
progress, managing the budget, and analyzing workloads.
Project creates budgets based on assignment work and resource rates. As resources are assigned to
tasks and assignment work estimated, the program calculates the cost, equal to the work times the
Tate, which rolls up to the task level and then to any summary task, and finally to the project level.
Each resource can have its own calendar. which defines what days and shifts a resource is available.
Microsoft Project is not suitable for solving problems of available materials (resources) constrained
production. Additional software is necessary to manage a complex facility that produces physical
goods.
1.2 Project Work Plan
Prepare a list of all tasks in the work breakdown structure, plus:

❖ Duration of task.
❖ Current task status.
❖ Task dependencies.
❖ Key milestone dates.
Step 1: How to start the application

1.1 To start with Microsoft Project, navigate to Start - All programs – Microsoft Office Project 2007.
1.2 After starting the project, the Gant chart view appears by default (same as Figure).
1.3 Depending on the information needed, it is possible to work in different views of the project data. When
starting a list of tasks or activities, it is easiest to start with Task
ROLL NO – 2028216 SUBJECT CODE : BTCS-506-18

Sheet View (WBS View).

1.4 To display Task Sheet View, navigate to View (Menu item) - More Views.
1.5 A new screen appears then select task sheet and click Apply (see Figure below).

1.6 Task sheet view appears with only few columns of data (see Figure below).

Step 2: Entering the project title

2.1 Navigate to File (Menu item) - Properties.
2.2 Enter the Title of the project as specified in the Lab1 Assignment and then click OK
ROLL NO – 2028216 SUBJECT CODE : BTCS-506-18

Step 3: Entering the start date for the project

3.1 To do so, go to Project (Menu item) - Project Information. Enter the Start date of the project as specified
in the Labl Assignment. Then click OK

Step 4: Inserting a new column on the Task Sheet

4.1 We will need a column for hierarchical order of tasks. As a result, we need to include in the Task Sheet
a column for WBS Code. To do so, Select Insert (Menu item) Column WBS and then click OK

4.2 Alternate way to add a new column is as follows:

ROLL NO – 2028216 SUBJECT CODE : BTCS-506-18

Highlight any column where you want to insert, right-click then select Insert Column, it is inserted to the
left side of the highlighted column.
After inserting a new column the view appears like on the figure below.

Step 5: Creating a unique WBS Code

5.1 After you add a WBS Column to the sheet, the next thing you need to do is to create a unique WBS
codes for each task/activity,
5.2 select Project (Menu item) - WBS-Define Code. You can now add a code that will prefix the number
sequence (for example, 1, 1.1, 1.1.1, etc, as specified in column #1 of Lab1 Assignment).
You can also create the numbering hierarchy.
5.3 For example, if we want to create four levels of hierarchy (like 1.1.1.1),
➢ select Numbers (ordered) in the first four rows of the sequence columns of the
➢ WBS code definition dialog box.
➢ To separate the numbers using periods, select the period in the separator column.
➢ Leave the two items Checked at the bottom of the screen as shown below

Step 6: Entering a task

ROLL NO – 2028216 SUBJECT CODE : BTCS-506-18

6.1 To enter a task, click the empty cell in the column named Task Name once and start entering the task
name as specified in the column # 2 of Lab1 Assignment.
6.2 The alternate way to do this is as follows :
Double click the empty cell in the column named Task Name for each task to show The Task Information
screen and Go to General tab. Enter the names of the tasks as given in the column # 2 of Labl Assignment.
Then click OR

The outcome of this step should look like a Figure below :

ROLL NO – 2028216 SUBJECT CODE : BTCS-506-18

Practical-2
Aim-2 : Study and usage of OpenProj or similar software to track the progress of a project.
Tracking Progress
• Network Diagram
• Gantt Chart:
o Bar chart format.
o Useful to monitor project status at any point in time.
• PERT Chart:
o Flowchart format.
o Illustrate task dependencies and critical path.
Project Progress Views
The View menu lists several views by default, Calendar, Gantt Chart, Network Diagram, Task Usage, and
Tracking Gantt. The Resource related views are: Resource Graph, Sheet and Usage. You can click More
Views to see additional Views.
Network Diagram
Let us look at the Network Diagram view. By selecting it we see the following:

2.1 GANTT CHART

➢ Select Gantt Chart view from the view menu.
➢ You'll have a spreadsheet where you can now enter information of all the activities i.e. task name,
duration, start date, end date, predecessors and various other fields.
➢ You can enter required information in two ways, in spreadsheet or when you double click on cell you
get pop up window in which you can enter all the information of that particular activity for
predecessor activity you need to write activity number.
➢ The SW itself will calculate start and end date.
➢ Now the Gantt Chart is complete.
On the View menu, click Gant Chart In the Task Name field, type a task name, and then press TAB
(Niorosoft Project enters an estimated duration of one day for the task followed by a question mario.He
Duration field, type the amount of time each task will take in months, Weeks, days, hours, or minutes. In or
ROLL NO – 2028216 SUBJECT CODE : BTCS-506-18

counting nonworkins time. (By default the time period will be days, but that can be changed to
hours,months, etc.), Press ENTER. It should look like the figure below.

• PERT Chart:
o Flowchart format.
o Illustrate task dependencies and critical path.

Critical Path Analysis

The critical path is used by project managers to monitor and control the project. It is called the critical path
as it depicts.
ROLL NO – 2028216 SUBJECT CODE : BTCS-506-18

PRACTICAL – 3

AIM : Prepration of Software Requirement Specification Document, Design Documents

and testing phase related documents for your project such as case study for (Library
Managemant System).

LIBRARY MANAGEMANT SYSTEM

GROUP NO : 2
SATYAM SINGH(CSE , 2028216)

DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING

LYALLPUR KHALSA COLLEGE TECHNICAL CAMPUS
JALANDHAR
ROLL NO – 2028216 SUBJECT CODE : BTCS-506-18

Table of Contents
1. Introduction:
1.1 Purpose
1.2 Scope
1.3 Definations,Ascronyms, and Abberviations
2. The overall description
2.1 Product Functions
2.2 User Characteristics
2.3 Constraints
3. Specific Requirements
3.1 External Interfaces
3.2 Functions
3.3 Logical Database Requirements
3.4 Design Constraints
3.4.1 Software
3.4.2 Hardware
3.4.3 Operating System
ROLL NO – 2028216 SUBJECT CODE : BTCS-506-18

1. Introduction
This software system can fulfill the requirements of "Library System" In this software, you can manage the
record Books, Students Record, Issue Book Record, Return Books Record, Stock in Library, Reports of Books,
Students. All the transaction which is doing manually will do with the help of computer. We use Visual Basic
as front end and Oracle 8i as backend for making this project. This software will helpful in searching the
Student Record, Books Record in Library. This software also checks the duplicate Book Entry, Student Roll
No. There will be no chance of duplicity. Because the Book No. will be unique. In any Class Student also
have their different Roll no.
We are using Oracle 8i as a back end in our project. Oracle 8i is the most popular database currently in use.
Various approaches to data management are:
Manual methods of data management Management of data and information
Convenient and efficient retrieval Updating operations
1.1 Purpose:
1.The purpose of software system can fulfill the requirements of "Library System" In this software, you can
manage the record Books, Students Record, Issue Book Record, Return Books Record, Stock in Library,
Reports of Books, Students.
2. It also maintains the record of books that means book name, book id, book auther, publisher, quantity etc.
3. Searching
1.2. Scope:
In this software, you can manage the record Books, Students Record, Issue Book Record, Return Books
Record, Stock in Library, Reports of Books, Students. All the transaction which is do manually will do with
the help of computer. This product is very important for school, college and university library system. It is
very simple to understand for simple naïve user. In this software duplicate entry is not possible. After entering
the data in database user can also take the detail of various books, students, issue record, return books record
in printing form.

This software will helpful in searching the Student Record, Books Record in Library. This software also
checks the duplicate Book Entry, Student Roll No. There will be no chance of duplicity. Because the Book
No. will be unique. In any Class Student also have their different Roll no. 1.3 Definitions, Acronyms, and
Abbreviations.:
frm: This abbreviation is used for Form.
sturee: This stand from student record bookree: This stand for book record
rpt: Used for report con: It stand for connection
rs: It stand for recordset text: It is used for all text box tool that is already available in VB 6.0
prbarl: It is used for progress bar.
2.The Overall Description:
ROLL NO – 2028216 SUBJECT CODE : BTCS-506-18

The front end tool used in Visual Basic- which has many advanced features as compared to character based
languages like c++, e etc. The VB6 is that software which can be directly inserted on the form and code
automatically executed. The main features are:
❖ RAD (Rapid Application Development)
❖ Special tools like timer controls and OLE HANDLING
❖ Other database connectivity with MS tools as well as Oracle
❖ Supports may user defined reports features, in built reports features and can supports crystal reports.
❖ Can be used for on line applications.
2.1 Product Perspective:
Developing a system is just like a manufacturing unit where some raw material and man power is used to
produce the goods- in computer system, the data and figures are fed to computer for processing. The results
produced by computer are called information and have value of its users. On the basic of information we can
take valuable decisions.A system is defined as the organized collection of components works in a coordinated
manner, to achievew an objective. There three main implications of a system i.e.
1. A system must have a predetermined objectives
2. There must be interrelationship and interdependence among the system components.
3. The objective of organization as whole has higher priority than the objective of an individual
component.
2.2 User Characteristics:

1. Organization: It means all the parts of a software system must be properly arranged in order an
structure.
2. Interaction: All the components of a system must interact with other components to achieve the
Objective.
3. Interdependence: One part of a system must depend upon other component for proper working. It
means the output of one part may be feed to the other component as input.
4. Integration: It means holism; which means the collection of all the components.
5. Central Objective: Each system must have one central objective.
2.3 Constraints:
Following are the important constraints that are used in this software before installation into the PC.
1. Recognition of need
2. Feasibility study
3. Analysis
4. Design
5. Implementation & Maintenance

3. Specific Requirements
3.1 Internal Interfaces:
Which are used to collect the data from sources within the organization and they are:
❖ Finance Reports
❖ personnel Staff
❖ Professional Staff
❖ System documents and manuals
ROLL NO – 2028216 SUBJECT CODE : BTCS-506-18

❖ User Staff
❖ Reports transaction documents
3.2 External Interfaces:
These are the outside tools used to collect the data from the system for designing and they are:
❖ Vendors
❖ Government documents
❖ Newspapers and professional journals
To collect the data properly, some tools are used and they are;
❖ Review of literature, procedures, and forms
❖ On-site observations
❖ Questionnaires
❖ Interviews

3.3 Functions:

❖ Sorting of data
❖ Searching
❖ Retrieval of data
❖ Manage the record
❖ Books Students Record
❖ Issue Book Record
❖ Return Books Record
❖ Stock in Library
❖ Reports of Books & Students

3.4 Logical Database Requirements:

1. Distributed Database System

For database, which is split across a network Oracle combines the data, which is physically located
on different database into logical database, which can be accessed by everyone.

2. Concurrent database users

Oracle 9.0 supports a large number of concurrent users accessing data at the same time. It maintains
certain locking mechanisms, which maintains consistency of data.

4. Oracle 9.0 Database Structure

Oracle 9.0 database structures can be divided into two parts:
1. Logical Structure
2. Physical Structure
Logical Structure
Logical, database can be divided into following different parts:
1. Table Space
ROLL NO – 2028216 SUBJECT CODE : BTCS-506-18

2. Schema Objects
Table Space is made up of one or more data files. The various schema objects, which are logically stored in
the Table Space, are actually stored in the data files.
Schema object are collection of different object of same user.
There are various schemas in Oracle 9.0 like :

➢ Table
➢ Index
➢ Sequences
➢ Synonymous
➢ Procedure
➢ Views
Physical Structure
Physical oracle 9.0 stores all the information into various files like:

➢ Control Files
➢ Redo Files
➢ Data Files
➢ Parameter Files

3.4 Design Constraints:

3.4.1 Hardware Requirement
➢ P III or P IV
➢ 128 MB RAM
➢ 1024 KB Cache Memory
➢ Hard Drives (Master & Slave)
3.4.2 S/W Requirement:
➢ VB 6
➢ ORACLE 9i
➢ MS OFFICE

3.4.3 Operating System:

➢ Window XP Service Pack II

3.4.4 Human Ware:

➢ One Programmer
➢ One Data Librarian
➢ Data Entry Operators (As per requirements)
ROLL NO – 2028216 SUBJECT CODE : BTCS-506-18

Practical-4
Aim-4 : Preparation of Software Configuration Management and Risk Management
related documents.
SCM defines a mechanism to deal with different technical difficulties of a project plan. In a software
organization, effective implementation of software configuration management can improve productivity by
increased coordination among the programmers in a team. SCM helps to eliminate the confusion often caused
by miscommunication among team members. The SCM system controls the basic components such as
software objects, program code, test data, test output, design documents, and user manuals.
The SCM system has the following advantages:
• Reduced redundant work.
• Effective management of simultaneous updates.
• Avoids configuration-related problems.
• Facilitates team coordination.
• Helps in building management; managing tools used in builds.
• Defect tracking: It ensures that every defect has traceability back to its source
Configuration management is a technique or discipline to systematically manage, organize and control
changes in the documents, codes, artifacts and other entities during the development life cycle.
Features of a good CM tools are:
• Ease for the developers to work simultaneously
• Ensuring that the developers don't over write watch others code
• Maintenance the history of everything.
List of Software configuration management tools available are:
• VSS-Visual source safe
• CVS-Concurrent version system
• Rational Clear Case
• SVN-Subversion
• Perforce
• TortoiseSVN
• IBM Rational team concert
• Razor
• IBM Configuration management version management
• Quma version control system
• Source Anywhere
Risks are the events that may lead to project failure of delay. There are 3 categories of risk:
1. Project Risk: - That affect the project schedule or resources.
2. Product Risk: - That affect the quality or performance of the software being developed.
ROLL NO – 2028216 SUBJECT CODE : BTCS-506-18

<PROJECT NAME>

NAME(BRANCH, ROLLNO)

CONFIGURATION MANAGEMENT PLAN

Version Number: 1.1

Version Date: <mm/dd/yyyy>

DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING

LYALLPUR KHALSA COLLEGE TECHNICAL CAMPUS
JALANDHAR
ROLL NO – 2028216 SUBJECT CODE : BTCS-506-18

VERSION HISTORY
[Provide information on how the development and distribution of the Configuration Management Plan will be
controlled and tracked. Use the table below to provide the version number, the author implementing the
version, the date of the version, the name of the person approving the version, the date that particular version
was approved, and a brief description of the reason for creating the revised version.]

Version Implemented Revision Approved Approval Description

Number By Date BY Date of change
1.0 <Author name> <mm/dd/yy> <name> <mm/dd/yy> <description of
change>
ROLL NO – 2028216 SUBJECT CODE : BTCS-506-18

TABLE OF CONTENTS
1. INTRODUCTION………………………………………………………………………….20
1.1 Purpose of The Configuration Management Plan.....................................................20
2. CONFIGURATION MANAGEMENT……………………………...……………………20
2.1 Approach…………………………………………………………………..……….20
2.2 Organization…….………………………………………………………….………20
2.3 Training.....................................................................................................................20
3. CONFIGURATION MANAGEMENT ACTIVITIES…………….…………………….20
3.1 Configuration Items..................................................................................................20
3.2Configuration Identification………………...………………………………………20
3.3 Artifact Life Cycle....................................................................................................21
3.4Configuration Control................................................................................................21
3.5Configuration Auditing/Reporting………………….……………………...……….21
APPENDIX A: CONFIGURATION MANAGEMENT PLAN APPROVAL….…………22
APPENDIX B:
REFERENCES………………………………………………..……………………………….23
APPENDIX C: KEY TERMS……....…………….…ERROR! BOOKMARK NOT DEFINED.
ROLL NO – 2028216 SUBJECT CODE : BTCS-506-18

Introduction
Purpose of The Configuration Management Plan
[Provide the purpose of the Configuration Management Plan.]
The overall objective of a Configuration Management (CM) Plan is to document and inform project
stakeholders about CM with the project, what CM tools will be used, and how they will be applied by the
project to promote success. The <Project Name> CM Plan defines the project's structure and methods for
• .Identifying, defining, and baselining configuration items (CI)
• Controlling modifications and releases of Cls
• Reporting and recording status of Cls and any requested modifications
• Ensuring completeness, consistency, and correctness of Cis
• Controlling storage, handling, and delivery of the Cis
The intended audience of the CM Plan is the project manager, project team, project sponsor and any senior
leaders whose support is needed to carry out communication plans.
Configuration Management
Approach
[Identify the recommended CM approach (make or buy). Justify why one option was selected of the other. If
purchasing a CM system, identify which system(s) were recommended as potential options and why one was
chosen over the others.]
Organization
[Identify items such as how CM activities will impact the organization, definition of roles and responsibilities
for those involved the CM activities and those impacted by them, what organizational policies and procedures
may be impacted, and any interfaces between other organizations that may impact the CM effort.]
Training
[Identify the kind and amount of training necessary to bring the performing organization up to speed on what
configuration management is, any tools used to perform CM activities, and what, if any, impact CM may have
on how work is performed. This may include development team orientation, tools training, organizational
awareness, etc.]
Configuration Management Activities
Configuration Items
[Identify what items will and will not be placed under CM.)
Configuration Identification
[Define how configuration items will be identified throughout the CM/Project life cycle. This section should
define identification schemas for information such as:
• Labeling and numbering documents and files
• Relationships between documents and files
• Addressing versions and releases
• Change Control Forms
• Various baselines for the project (product versioning)]
ROLL NO – 2028216 SUBJECT CODE : BTCS-506-18

Artifact Life Cycle

[Define the artifact life cycle for the different Cls under CM]

Configuration Control
[Define how configuration items will be controlled throughout the CM/Project life cycle. This section
should define procedures for items such as:
• Changing baselines
• Processing and managing change requests and Change Control Boards (CCBs) Communicating
configuration status
• Performing configuration audits
• Building, testing, and debugging workspaces
• Who owns what product code and how to appropriately work with that code]

Configuration Auditing/Reporting

[Define how configuration items will be tracked, measured, and reported.]

ROLL NO – 2028216 SUBJECT CODE : BTCS-506-18

Appendix A: Configuration Management Plan Approval

The undersigned acknowledge that they have reviewed the <Project Name> Configuration Management
Plan and agree with the information presented within this document. Changes to this Configuration
Management Plan will be coordinated with, and approved by, the undersigned, or their designated
representatives.
[List the individuals whose signatures are desired. Examples of such individuals are Business Owner, Project
Manager (if identified), and any appropriate stakeholders. Add additional lines for signature as necessary.]
Signature ____________________________________ Date: __________________
Print Name: ____________________________________
Title: ____________________________________
Role: ____________________________________

Signature ____________________________________ Date: __________________

Print Name: ____________________________________
Title: ____________________________________
Role: ____________________________________

Signature ____________________________________ Date: __________________

Print Name: ____________________________________
Title: ____________________________________
Role: ____________________________________

APPENDIX B: REFERENCES
[Insert the name, version number, description, and physical location of any documents referenced in this
document. Add rows to the table as necessary.]
The following table summarizes the documents referenced in this document.

Document Name Description Location

<Document Name and Version <Document description> <URL or network path where
Number> document is located>
ROLL NO – 2028216 SUBJECT CODE : BTCS-506-18

Practical-5
Aim-5 : Study and usage of any Design phase CASE tool.
Relational rose
1. Rational Software:
Rational Machines was founded by Paul Levy and Mike Devlin in 1981 to provide tools to expand the use of
modern software engineering practices, particularly explicit modular architecture and iterative development.
2. Rational Environment
The Rational Environment was organized around a persistent intermediate representation (DIANA), providing
users with syntactic and semantic completion, incremental compilation, and integrated configuration
management and version control. To overcome a conflict between strong typing and iterative development
that produced recompilation times proportional to system size rather than size-of-change, the Rational
Environment supported the definition of subsystems with explicit architectural imports and exports; this
mechanism later proved useful in protecting application architectures from inadvertent degradation. The
Environment's Command Window mechanism made it easy to directly invoke Ada functions and procedures,
which encouraged developer-driven unit testing.
The company's name was later changed from "Rational Machines" to Rational to avoid emphasizing this
proprietary hardware.
Rational provided code generators and cross-debuggers for then-popular instruction set architectures such as
the VAX, Motorola 68000, and X86; much of this was accomplished through a partnership with Tartan Labs,
founded by Bill Wulf to commercialize his work on optimizing code generators semi-automatically produced
from architecture descriptions (PQCC),
3. Organization
Rational's field organization was noteworthy for its team-based approach to customer success. Sales teams
were led by an account representative, and included 3 to 5 software engineers referred to as technical
representatives (techreps). Sales teams engaged with their customers both pre-sales and post-sales, and were
held accountable for customer success as well as for revenue targets. This approach encouraged deep
engagement between techreps and customers, which in turn helped Rational develop a significant experience
base in the successful development of complex long-lived software. The Best Practices underlying the later
Rational Unified Process (RUP) - iterative development, component-based architecture, modelling,
continuous developer-driven testing, requirements management, and automated testing are all traceable to this
experience base.
4. Second-generation products
In 1990, Rational launched three parallel development efforts: re-implementation of the Rational Environment
(for Ada) to run on Unix-based workstations from Sun and IBM, development of a comparable Rational
Environment for C++ to run on Unix-based workstations from Sun and IBM, and development of a
workstation hosted modeling tool called Rose that supported a graphical notation developed by Grady Booch.
Apex, the Rational Environment for Ada, was launched on Sun and IBM Unix platforms in 1993, and the
Rational
The latter, which allowed prospective customers to analyze existing C++ code to produce "as-built" navigable
class diagrams, helped overcome Rational's late re-entry into the market for object-oriented modeling tools.
Rose 2.0 ran on Windows PCs and on several Unix-based workstations.
ROLL NO – 2028216 SUBJECT CODE : BTCS-506-18

5. Acquisitions
The momentum generated by Rose and the UMI. enabled Rational to establish a partnership with Microsoft,
which then saw model-based development as a means of attracting enterprise-scale developers to the Windows
platform, Rational's aim was to secure Microsoft's public support for modelling in the software development
process. This engagement with Microsoft convinced Rational to address the broader Windows-based IT
market.
PROCEDURE:
UML Diagrams of Hotel Management System
❖ Use Case Diagram of Hotel Management System
Use case Diagrams are central to modeling the behavior of a system, subsystem, or a class. Use case diagrams
are important for visualizing, specifying, & documenting the behavior of an element.
ROLL NO – 2028216 SUBJECT CODE : BTCS-506-18

❖ Class Diagram of Hotel Management System

Class diagram shows a set of classes, interfaces, and collaborations and their relationships. Class diagrams
are not only important for visualizing, specifying & documenting structural models, but also for constructing
exe

1. Class diagram for Booking Rooms In Hotel

ROLL NO – 2028216 SUBJECT CODE : BTCS-506-18

II. Class diagram for Room Search In Hotel

❖ Component Diagram For Hotel Management

A component diagram shows the organization and dependencies among a set of components. This involves
modeling the physical things that reside on a node, such as executables, libraries, tab, files, and documents.
ROLL NO – 2028216 SUBJECT CODE : BTCS-506-18

❖ Deployment Diagram Of Hotel Management System

Deployment diagram shows the configuration of run time processing nodes and the components that live
on them. It is used to model the static deployment view of a system.
ROLL NO – 2028216 SUBJECT CODE : BTCS-506-18

❖ Collaboration Diagram
Collaboration names a society of classes, interfaces, and other elements that work together to provide some
cooperative behavior that's bigger than the sum of all its parts.
ROLL NO – 2028216 SUBJECT CODE : BTCS-506-18

❖ Sequence Diagram of Hotel Management System

❖ State Chart Diagram:

A start chart diagram is normally used to model how the state of an object changes in its lifetime. They are
good at describing how the behavior of an object changes across several use case executions.
ROLL NO – 2028216 SUBJECT CODE : BTCS-506-18