INTRODUCTION THE PROJECT CHAPTER 1

1.1 PROJECT SUMMARY

Aim: To implement a software application which involves the planning, monitoring, and
control of peoples (men power), process and events that occur during the project
development session.
Software is used in any organization, to coordinates the project management activities
during the project (Exterior or Interior planning/execution) session and manages the
project task assigned to different employee/trainee in different department of an
organization. Finally it involves the report generation of different project development
activities. The project management activities involve assigning and managing the
employee tasks, meeting establishment, messaging services etc. The system shall be used
with any number of users at the same time and shall not degrade in the performance.
In terms of the project (designing of the Interior/Exterior layout of structure) is follows
the some similar step of S/W Engineering process, like a requirement specification,
analysis, designing and implementation of the design. So here project involves the deep
analysis of the project management concepts, which includes the number of meeting with
the company’s employees. The different methodologies of the project development have
been studied during the development session and select the best according to our context.
Regular meeting with our project guide the requirement prepared specification documents
for the next phases of the project development. By the observation in the organization,
We found some problems which is easily handle by the computer, like after completion of
one phase of the project then assignment go to some other department can be take the
more time, so overall project development can be take the more time. Reading and
reviewing the requirements, the different analysis model is prepared for the proper
designing of the system. Each document is then used in the different designing modules
such as database designing, OMT analysis and algorithm design. After the end of the each
phase of our project development, the meeting with the project guided was held for the
feedback and the improvement process. The guide the implementation is then started
approved once the work.

CICA\MCA\PRJ29 -1- ACE Associates

INTRODUCTION THE PROJECT CHAPTER 1

1.2 PURPOSE

The purpose of this project is to plan, control, and manage the different activities of the
project development session. In another words there will be a centralize control and
monitor over the different projects running into the organization. It is intended to any
organization that are usually involves in the long term project about 1 to 2 years of time
duration. The project will keep track of each of the project activities, which might be the
part of the project development. The project is designed to provide the task distribution
of the large project among the many people round about 20 - 30 employee as well as
trainee of an organization. Their project assignment details are stored into the system
database for their future evolution. The project is able to distribute the project assignment
in different level of organization. One of the important intentions of this project is that it
will divide the project in three different levels. The first level is milestones which is abstract
partition of the whole project in three different levels. These milestones are assigned to
particular departments assignment, which shall again divided into the employee
assignments.
Another important function of the project is to provide the security on the different
milestones or phases of the projects. The next intention is that if any of the assignment is
lagging by its deadline, all the people which come at the seniority level with respect to the
responsible person on that assignment shall automatically receive the notification message
of this situation. The project also enables the user to record the meeting schedules.
In addition to this feature, the project is also design to provide the inbuilt messaging
services, monthly and quarterly assignments reports. The messaging services enable the
user to send and receive the message from and to the employee, which are registered into
this system. There is no any intention to provide the global messaging services. It is limited
to the group of people in the organization. The reporting services enable the user to take
the hard copy in very good format, which shall describe the project and its activities in
detail.
The project is also keep track on the total execution coasting of the project. Another
feature of this system is that, organization taking the backup of its data (Designs of the
structure) 4 times in the year, so whenever management need to refer the past project at
that time it is very difficult for them to identify that, what particular project is resides in
which CD’s, or where is its last modified backup. So this is handled by this system.

Assignment of the work for particular labor agencies at that time we need to identify its
past record or total work load at this time for that agencies. For the very big or commercial
project organization issuing the tender for the different material agencies and all the
agencies are beading for that tender, and this beading process is handled at the

CICA\MCA\PRJ29 -2- ACE Associates

INTRODUCTION THE PROJECT CHAPTER 1

organization for the particular time. Agencies are changing his prices many times within
the time period.

1.3 PROJECT SCOPE

In order to develop a reasonable project plan, it is required to functionally bind

characteristics of the software. So that by following the software engineering principles,
the project management activity is the determination of software scopes. By considering
the followings objectives of software scopes, we derived the software scope statements.
 Software scope must not be ambiguous and understandable at management and
technical levels.
 A statement of software scope must be bounded.
 There must be a quantitative data.
Software scope is defined by addressing context, information objectives, and function and
performance.

1.3.1 Context
APMS is a project management system which could be a part of any organization which
handle its resources efficiently and optimal.

1.3.2 Information Objectives

Individual employee or trainee task details, individual department task detail, project
milestones details, previous developed project detail, evolution chart of individual
employee, project status detail, meeting establishment, discarded project details, agencies
(labor or material) detail, assignment detail, backup data detail stage wise etc, are the
customer visible data objects produced as output from the software. Project details,
Employee details, department details, different project role details, agencies detail are the
visible data objects required for input to derive suggested output.

CICA\MCA\PRJ29 -3- ACE Associates

INTRODUCTION THE PROJECT CHAPTER 1

1.3.3 Functions and performance

Major function of the software is to provide different phase’s milestones and its derived
assignments with respect to different project role. The project milestones divisions,
department task divisions, employee task divisions, assigning the different access rights
on different project role such as project leader, department head, team leader,
administrator, assigning the general system rights on designations, changing the access
rights, finalizing the projects, messaging services are the another function area which the
software should performs.

1.3.4 Obtain the exact software scope statement

“The Architectural project management system is a project management system
which shall configured the project management activities such as the project distributions
among the number of people, tracking the long terms projects having the details of each
task of projects, assigning the project role and responsibility in the project development
session, provides the evolution module of the employee according to their performance in
the project, provides the automatic information mechanism in certain unaccepted situation
like deadline of the individual task is exceed by time, provide the internal messaging
services and document submission facilities to bridge the communication bridge between
the project team and member, provides the search engine for search the data from the
past backup CDs, also handle the total project coasting and assigning the agencies for
particular work in the project.”

1.3 OBJECTTIVES

1). AN APMS shall facilitate the user to enter the details about the
organizations and details of projects.
 General role specification on the system which shall provide the access
rights on the system access. This role is associated with the designation of
employee.
 Designation creation, department creation and employee registration.
 The project information like starting date, ending date, approximately
ending date etc.
 The project role specification in the different projects. This role identifies the
user’s rights on different projects. The role may be project leader or team
leader.

2). AN APMS shall facilitate the user to divide the project into different
milestones and its subtask assignments.

CICA\MCA\PRJ29 -4- ACE Associates

INTRODUCTION THE PROJECT CHAPTER 1

 A project is divided into milestone and defines the project leader

Who is responsible for assigning these project milestones.
 Milestones is divided into department task assignments by making
the team leader for the department task.
 Department task assignment is divided into employee a task which
is assign to individual employee.

3). APMS shall facilitate the user to track the project as per the role of
employee.
 The administrator shall have the full access on the project as well as its
divisions.
 The project leader shall have full access on the project on which he is assign
as project leader.
 Employee or trainee does not occupy any rights on any phases of this project
division.
 The rights may be change any time as per the requirement once
the it is configured in the system.

4). AN APMS shall facilitate the user to generate the reports of the projects as
well as different employee’s and department’s assignments.
 Project detail with full division tracking.
 Employee evolution points report on different project.
 Coasting report for project.
 Agencies report which getting the total work from the project.
 Individual department task and employee task detail.
 Drawings are issued to agencies for the project.

5). An APMS shall have the automatic message informer which shall inform
the seniors when certain unaccepted events occur during the project
development. i.e., deadline exceed by the time, assignment complete etc.

6). In the APMS shall have the messaging services to bridge the
communication gap.
End of Chapter 1

CICA\MCA\PRJ29 -5- ACE Associates

INTRODUCTION THE PROJECT CHAPTER 1

2.1 CHAPTER OBJECTIVES

Management remains a very necessary activity when computer based system and products
are building. Building computer software is a complex undertaking because there is always
groups of logic integrated with each other to meet certain requirements and even if the
logic has been developed according to requirements are always subject to changes. The
simple says is that every thing is permanent except change. That’s why the project needs
to be managed.
The project planning involves estimation attempt to determine how much money, how
much effort, how many resources and how much time will take to build a specific system
or product. In simple state it would never possible to build a house how much you are
about to spend. A project plane is produced as management activities commence. The
plan defines the process and plane to be conducted, the people who will do the work, and
the mechanism for assigning risk, controlling change and evaluating quality. We had
followed the following project management concepts during our project development
sessions, which are already adopted by the software engineering.

2.1.1 Management concepts:

 Management activities involve planning, monitoring, and control of the people,
process, and events that occur as software evolves from preliminary concepts to
an operational implementation.
 Software project management is an umbrella activity with in software engineering.
It begins before any technical activity is initiated and continues through out the
definition, development and support of computer software.
 The project management activity encompasses measurement and metrics,
estimation, risk analysis, schedules, tracking and control.
By studying this concept in depth we started to our management activities, which are
listed in this chapter. By reading this chapter you would immediately our project
development efforts and strategy.

2.2 PROJECT DEVELOPMENT APPROACH AND JUSTIFICATION

2.2.1 Introduction
Because software, like all capital, is embodied knowledge, and because that knowledge is
initially dispersed tactic, latent, and incomplete in large measure, software development
is a social learning process. The process is dialogue in which the knowledge that must
become the software is brought together and embodied in the software. The process
provides the interaction between user and designers, between users and evolving tools,

CICA\MCA\PRJ29 -6- ACE Associates

INTRODUCTION THE PROJECT CHAPTER 1

and between designers and evolving tools and technology. It is an interactive process in
which the evolving tool itself serves as the medium for the communication, with each new
round of the dialogue electing more useful knowledge from the people involved.

Software process model is an abstract representation of a software process. Each process

model represents a process from a particular prospective so only provides partial
information about the process. Rather, they are useful abstraction, which can be used to
explain different approaches to software development. For many large systems, of cause,
there is no single software process that is used. Different process is used to develop
deferent part of the system.

Due to the reason different processes approach is used in different phases of software
development we have used number of different process models such as waterfall model,
OMT methodology, UML, testing strategy etc.

2.2.1.1 Water fall model

This model is used widely in the field of software engineering especially when the software
product needs to be launch into the commercial market initially with the limited
functionality and when the time is very short for the project development. We are two
people in a team member working on this project and with in 5 months of time duration
we had to deploy this project. Another reason to choose this model is that we have a
limited set of requirements which is not subjected to changes, so we did not require back
tracking in the development process. The software development process model that we
found can be represented by the following figure

CICA\MCA\PRJ29 -7- ACE Associates

 INTRODUCTION THE PROJECT CHAPTER 1

PROCESS MODEL (LINEAR SEQUENTIAL MODEL)

ANALYSIS PHASE

1. REQUIREMEN
T
ENGINEERING
DESINING PHASE
2. OBJECT
MODELLING

3. DYNAMIC 1. PARTITIONING IN
MODELLING TO SUBSYSTEMS

2. SOFTWARE IMPLEMENTATION
4. FUNCTIONAL
MODELING COMPONENTS PHASE
DESIGNING
1. IMPLEMENTING
DATABASE
3. DATABASE
DESIGNING
2. IMPLEMENTING
BUSINESS LOGIC
4. GUI DESIGNING
3. IMPLEMENTING
5. ALGORITHM
REUSABLE
DESIGNING
COMPONENTS

4. IMPLEMENTING GUI

TESTING

1. UNIT TESTING

2. INTEGRATION
TESTING

3. TEST REPORTS

4. REMOVING ERRORS

DOCUMENTATION
AND
DEPLOYMENT

CICA\MCA\PRJ29 -8- ACE Associates

INTRODUCTION THE PROJECT CHAPTER 1

Analysis:
If you do not analyze, it’s highly likely that you will build very elegant software.
Solution is that solves the wrong problem. The result is wasted time and money, personal
frustration, and unhappy customers. In this phase we identified data, functional and
behavioral requirements and by electing information from the company’s management
department. Requirements are refined and analyzed to assess their clarity, completeness
and constituency. A specification incorporating a model of the software is created and then
validated by both our project guide and management department. We studied different
analysis methodology such as OMT, UML. The models developed are object modeling,
dynamic modeling and functional modeling which follow the OMT and UML concepts.

Designing:
We would not attempt to build a house with out blueprint, would we? We have risk
confusion, errors and other environment problems. Computer software is considerably
more complex then a house; hence we need a blueprint – the design. This phase begins
with the requirements model. We work to transform this model four levels of design
details; the data structure, database, the system architecture, component design and
finally GUI designing. Also according to the OMT methodology, we also design the object
framework, which would be deployed during the implementation phase.

Implementation:
Once you design the system the remaining work is work is to implement the designed
data in this phase we started by implementing the database on the database server and
then implement the business logic, which is designed during the object modeling. The
application GUI implementation, component implementation is the next step in these
phases.

Testing:
Testing often accounts for more project effort then any other software engineering activity.
If it conducted haphazardly, time is wasted, unnecessarily efforts are expanded, and even
worse, errors sneak through undetected. It would there fore seem reasonable to establish
a systematic strategy for testing software. Testing begins “the small and progress to the
large”. By this we mean that early testing focuses on a single component and applies white
–and black box tests to uncover errors in program logic and function. After individual
components are tested they must be integrated. Testing continues as the software is
constructed.

Documentation and deployment

CICA\MCA\PRJ29 -9- ACE Associates

INTRODUCTION THE PROJECT CHAPTER 1

This is final stage for the project development process, which follows the waterfall model.
In this phase of the software development session integrate the previously developed
document. Finally install the software project in real world of computer profession.

2.2.1.2 OMT
During the selection of the right methodology for this project we found that OMT (object
modeling technique) would be useful to model a system from three related but different
viewpoints, each capturing the important aspects of the system. This methodology helps
us to represent the whole system in three different viewpoints of the modeling system.
The object modeling represents the “static data” aspect of the system. The dynamic model
represents the temporal, behavioral, “control” aspect of the system. The three kinds of
model separate a system into orthogonal views that can be represented and manipulated
with a uniform notation. The key benefits are that software engineering methodology is a
process for the organized production of software, and OMT methodology entire software
life cycle. Testing and maintenance is also supported by the OMT but was not used by us.
Some of the important concept of the in the OOT are the abstraction, encapsulation and
polymorphism.

Abstraction
Abstraction is the tactic of stripping an idea or object of its unnecessary accompaniments
until you are left with its essential, minimal form. A good abstraction clears away
unimportant details and allows you to focus and concentrate on the important details.
Abstraction is the important software principle. A well-designed class exposes a minimal
set of carefully considered methods that provide the essential behavior of the class in an
easy-to-use manner. Unfortunately, creating good software abstraction usually require a
deep understanding of the problem and its context, great clarity of thoughts, and plenty
of experience. In short Abstraction is Selective Ignorance.
The purpose of abstraction is not to be vague, but to create a new semantic level in which
one can be absolutely precise.

Encapsulation:
Encapsulation can be defined as the “the packaging of a collection of items. Encapsulation
encompasses the responsibility of class, including attribute and operations, and the states
of the class, as defined by specific attribute value. There are two important aspects of the
encapsulation
1. Combining the data and function in the single entity and
2. Controlling accessibility of the entity members

CICA\MCA\PRJ29 - 10 - ACE Associates

INTRODUCTION THE PROJECT CHAPTER 1

Polymorphism: Polymorphism is a characteristic that greatly reduces the effort required

to extend and existing OO system. This mean that there can be one or two meaning of the
same entity we can define. This fetcher helps us in maintenance with the software
application. Because whenever there is a new object has been added to the system there
is no confusion with the existing implementation function or property. It can be different
definition but with same name.

Inheritance: inheritance is the one of the key differentiator between conventional and
OO systems. Inheritance is the process in which the properties and methods are inherits
to another class of the system without writing the simple code even. This is the reusable
concept that can help to develop the application code with the fewer burdens.

2.2.1.3 UML
To represent the object modeling technique, which we followed, we used one standard
known s UML (UNIFIED MOIDELINF LANGUAGE). James Rambaugh has collaborated to
combine the best feathers of their individual object-oriented analysis and design method
into unified method. The result called the Unified Modeling Language.
The unified modeling language is the general- purpose visual modeling language that is
used to specify, visualize, construct, and document the artifacts of a software system.
It captures the decisions and understanding about system that must be constructed.

2.3 PROJECT SPECTRUM

2.3.1 Objectives
Once the product objectives and scope are understood, the next step is to consider the
deadline of the project, and the team members who are working on a project. With in a
limited time and limited human power, partitioning it into the milestones shall develop the
project. A software process provides the framework from which a comprehensive plane for
software development can be established. A small number of framework activities are
applicable to all software projects, regardless of their size or complexity. A number of
different task sets, tasks, milestones, work products and quality assurance points-enables
the framework activity to be adapted to the characteristics of the software project and the
requirements of the project team.
We conduct planned and controlled software projects for one primary reason it is the only
known way to manage complexity. We divide the whole project activities into the following
milestones, which shall be achieved in sequence.
This is only for the entire purpose of the software development not for the client or
customers. This is the sequence in which we would like to develop the project.

CICA\MCA\PRJ29 - 11 - ACE Associates

INTRODUCTION THE PROJECT CHAPTER 1

2.3.2 PROJECT MILESTONE

MILESTONE NAME PROJECT ACTIVITY START DT. END DT.

Project management Project Request Later. 8th Aug, 15th Aug,
and planning Project Confirmation Later. 2005 2005
Manage the people.
Requirement Meeting with client. 15th Aug, 30th Aug,
collection Requirement specification. 205 2005
Authors requirement engineering.
System analysis Studying existing system. 1st Sept 10th
Studying the concepts. Sept
Feasibilities studies etc.
Develop object Identify object classes. 12th Sept 20th Sept
modeling Keeping right classes.
Identifying associations etc.
Developing dynamic Preparing scenario. 21st Sept 1st Oct
modeling Identifying events.
Building a state diagram etc.
Developing Identify the input and outputs. 10th Oct 15th Oct
functional modeling Building dataflow diagrams.
Describing functions etc.
Design database Identify the table names. 17th Oct 25th Oct
Identify the naming convention.
Prepare ER-Diagram.
Identify Relation Ships.
Prepare Data Dictionary.
Designing GUI Requirement study. 27th Oct 5th Nov
Studying hardware compatibilities.
Studying the resolution of display.
Implement the Create table. 7th Nov 12th Nov
database on server Prepared relationship diagram.
machine Creating User.
Implement the Implement the object classes. 14th Nov 19th Nov
business logic Create the assembly file
Implement the user Design the forms. 19th Nov 15th Dec
interface

CICA\MCA\PRJ29 - 12 - ACE Associates

INTRODUCTION THE PROJECT CHAPTER 1

Unit testing Prepare test cases. 16th Dec 18th Dec

Prepare the testing reports.
Resolve the errors.
Integrated testing Debug the system. 18th Dec 20th Dec
Prepare the test cases.
Prepare the testing reports.
Resolve the errors.
Documentation Integrate the prepared documents, 8th Aug 25th Dec
formatting etc.
Deployment Secure hardware resources. 22nd Dec. 22nd Dec,
Secure software resources. 2005

TABLE 2.1 PROJECT MILESTONES LIST AND MILESTONE ACTIVITIES

Each of this milestones shall be completed with in the limited time which is indicates in
the estimated ending field in the table. The related activity for the specific milestones is
listed in the project activity column. This is the over all sketch of the whole project
development process which we indented to plane and succeed in that approximately 99%
of accuracy.
The next session shows the team management, which we had followed in out project.

2.4 PROJECT SCHEDULING

In order to build a complex system, many software engineering tasks occur in parallel,
and result performed during none task my have a profound effect on work to be conducted
in another task. These interdependencies are very difficult to understand the without a
schedule. It’s also virtually impossible to access progress on or large software project
without a detailed schedule.
The software engineering tasks dictated by the software process model are refined for the
functionality to be built. Effort and duration are allocated to each task and a task network
is created in manner that enables the software team to meet the delivery dead line
established. For the project scheduling: compartmentalization, interdependency, time
allocation, effort validation and defined responsibilities.

2.4.1 COMPARTMENTIZATION AND IT’S DEFINED OUTCOMES

We had compartmentalization the whole project development into a number of
manageable activity and tasks. The tasks and activities related to different development
phases are represented into following table.

CICA\MCA\PRJ29 - 13 - ACE Associates

INTRODUCTION THE PROJECT CHAPTER 1

ID TASK NAME TASK ACTIVITY OUTCOMES

Analysis/Software Requirement
1 Conduct needs analysis Existing system study, internet surfing, Problem
examining feasibilities, prepare analysis understanding,
model feasibility
reports,
analysis model
2 Draft preliminary software Meeting with companies employee, Requirement
specification. prepare rough sketch of requirements, collection in
collect additional software information rough papers
3 Review Discuss with team members, project Team members
Software specification leader, and entire faculty guide. and project
With team leaders
justification
4 Incorporate feed Refine the requirements, prepare the SRS documents
Back on SRS documents
Software specifications

5 Develop delivery timeline Project scheduling, estimate time line Estimated time
chart for project completion line charts and
effort allocation
Design
6 Object model designing Analyze the objects, identify the right Object
objects, object relation ships etc. modeling
followed by
UML
7 Event identification and Identify the events, report of sequential Events trace
sequences diagrams of events documentation
8 Sate diagram State identification, dynamic modeling Dynamic
of states modeling
documents
9 Identify the functions, Tracing the inputs to system, tracing Predefine
inputs and outputs the outputs of system, etc outputs and
inputs
documents

CICA\MCA\PRJ29 - 14 - ACE Associates

INTRODUCTION THE PROJECT CHAPTER 1

10 Prepare functional model Prepare the data flow diagrams Functional

using data flow diagrams modeling
documents
11 Design the database Identify the tables, identify the table Data base
relation ships, and identify the relation ships
Constraints, table data types diagrams
12 Design algorithms Objects functions pseudo code Pseudo code to
preparation achieve the
targeted
functionality
13 Design screen layouts and Review the user requirements, prepare Actual
components the GUI documents implementation
of user
interface

Development

14 Review function diagrams -

and screens
15 Implements database Implement tables, implements stored Deployed
procedure, data base relation database
server
16 Implement business logic Object class implantation, property and Deployed .dll
function definitions. files on server
machines
17 Implements software Develop reusable components, deployed Deployed
components integrate with the application. component.
Dll’s
18 Implements user interfaces Web page graphics and images Integrated
designing, web component designing components,
business logics
and images on
the web pages
TESTING
19 UNIT TESTING

CICA\MCA\PRJ29 - 15 - ACE Associates

INTRODUCTION THE PROJECT CHAPTER 1

20 Review modular code Check the function of each web page, Testing
each object class modules
reports
21 Test component modules to Debug the modules, prepare test cases, Test case
product specifications report the error resolve efforts etc. reports
22 Identify anomalies to Check whether the module of develop Unit testing
product specifications code works as per the requirements or approval
not
23 Modify code Chang the code; report the changes, re Refined code
debugging of changed code
24 Retest modified codes Retesting of each modified code once -
again
Documentation
30 Prepared documents Report generation -
integrations
31 Prepare new required Report generation Final project
documents report

Deployment and submission

32 Determine final deployment Securing time
strategy and date of
project
deployment
33 Secure deployment Secure hard
resources water and
software
34 Deploy software Running
software

Inter dependency
In above table there are different tasks of different project development phases are
defines. The inter dependency of each compartmentalized activity or task must be
determined. Some tasks must occur in sequence while others can occur in parallel. Some
activates cannot commence until the work product produced by another is available. The
activity can occur interdependently.

2.4.2 TIME ALLOCATION AND DIFINED RESPONSIBILITIES

CICA\MCA\PRJ29 - 16 - ACE Associates

INTRODUCTION THE PROJECT CHAPTER 1

Each task to be scheduled must be allocated some number of work units. In addition, each
task must be assigned a start date and a completion date that are a function of the
interdependencies and whether work will be conducted one full-time or part time base.
Every task that is scheduled should be assigned to specific team members.
The next sheet shows the time line chart, which indicated the dependencies, estimated
ending dates and starting dates or each tasks.
End of Chapter 2

CICA\MCA\PRJ29 - 17 - ACE Associates

INTRODUCTION THE PROJECT CHAPTER 1

3.1 CHAPTER OBJECTIVES

This chapter is indented to describe the different type of user and their characteristics
according to the software, hardware and software specification which shall be used during
the software deployment. If you are a person who needs to learn or know about the project
and its functions only you may skip this chapter, because it is actually for those people
who is interested to purchase this software and used for its entire organization. This
chapter helps you to calculate your estimate when you actually deployed this software in
your organization.

3.2 USER CHARACTERISTICS

3.2.1 User basic knowledge

As this software is used in the commercial field with highly educated people and the very
big business firm there is not doubt that the user may not have the basics understanding
of the computer knowledge. But the user may not know the concepts, which we had
implemented in this software, so that each user shall have the following basics knowledge,
so that he/she can effectively use this software.

Users should have the awareness of the project access and his responsibility in his
Organization.

3.2.2 Type of User

According to the project leader Mr.Ashish Patel, there are mainly five types of user who
will this software in different context.

Administrator
This user maintains the security, make the project entry in the system, can define the
milestones, can define the department tasks, can create employee tasks, can rollback the
works and can evaluate the employee and make sure that the system keeps running
efficiently. This user can create the project leader, Department head, team leader and can
remove any employee from the system. This user has a full access on the system database.

CICA\MCA\PRJ29 - 18 - ACE Associates

INTRODUCTION THE PROJECT CHAPTER 1

Project Leader
This leader has a full access on the project, which is running under his responsibility. The
administrator of the system creates this user. Project leader can divide the project into
the project milestone, can create the department work, can create assign the employee
work. These users can rollback the department as well as employee works. He can define
the team leader for the department work, or even remove the employee from the system.
The user has only access in the database which comes under his assigned projects.

Department Head
This user shall have all the access on the department’s assignment. This user is defined
by the administrator. He define the employee’s work, can rollback the employee’s work.
He can define the team leader for the specific type of department work. He can change
the employee on a particular task.

Team Leader
This user shall have all the access on the particular team which is associated with one of
the department tasks. The user is defined by the department head, project leader, and
administrator of the system. The team leader is interface between project management
and developers. The team leader is responsible for ensuring that a task is allocated and
monitored to completion. The team leader is responsible for ensuring that development
staff follow project standards, and adhere to project schedules.

Employee
This user shall not have the access on the database. He can only change the status of his
assignment. He is not able to rollback his own assignment, rather he can only send the
request to his senior faculty of the organizations.

3.3 TECHNICAL SPECIFICATION

If you decide to use this software into your organization, you may require following
minimum resources to deploy this application. These are very minimum requirement to
start and run the application, but if you can effort higher resources then listed, the
performance would be better. The first table shows the hardware specification, and the
very next table list the software requirements.

CICA\MCA\PRJ29 - 19 - ACE Associates

INTRODUCTION THE PROJECT CHAPTER 1

Resource name Deployed location Required Recommended

Processor Server 500 GHz or higher 1.4 -GHz speed

Client 800 MHz or higher 1.4 GHz speed
Operating System Server Windows NT 4.0 Windows server
with service pack 6 2003(.net
framework 1.1
installed)
Windows 2000
professional
Windows
millennium with
service pack 3
Windows XP home
edition
Windows XP
professional edition

Client Any O.S

Memory Server 256 MB of RAM or 512 MB of RAM
higher
Client 128 MB of RAM 256 MB of RAM
Hard disk Server 10 GB of hard disk 40 GB if user are
free space more and project
are more
Client 5 GB of hard disk 10 GB Of hard disk
free space
Display Server 1024 * 678 or 32-bit true color
higher resolution
with 256 true color
Client 1024 * 678 or 32 -bit true color
higher resolution
with 256 true color
Input Device Server Mouse and
Keyboard
Client Pointer device like
Mouse

CICA\MCA\PRJ29 - 20 - ACE Associates

INTRODUCTION THE PROJECT CHAPTER 1

Keyboard
Network Card Server/Client 100 MBPS duplex
mode

3.3.2 Software specification:

Software needed on the server : Microsoft dot net frame work 1.1
Crystal report 8.0
SQL server 2000 Server component

Software needed on the Client : Microsoft dot net frame work 1.1
Crystal report 8.0
SQL server 2000 Client component

END OF CHAPTER 3

CICA\MCA\PRJ29 - 21 - ACE Associates

INTRODUCTION THE PROJECT CHAPTER 1

4.1 CHAPTER OBJECTIVES

The written word is a wonderful vehicle for communication, but it is not necessarily the
best way to represent the requirements for computer software. Analysis modeling uses a
combination of text and diagrammatic forms to depict requirements for data, function and
behavior in a way that is relatively easy to understand, and more important,
straightforward to review for correctness, completeness and constancy.
To validate software requirements, we need to examine them from a number of different
points of view. Analysis modeling represents in three ‘dimensions’ thereby increasing the
probability that errors will be found, that is inconsistency will surface, and that omissions
will be uncovered.
In this chapter data, functional and behavioral requirements are modeled using a number
of different diagrammatic formats. Data modeling defines data objects, attributes, and
relationships functional modeling indicates how data are transformed within a system.
Behavioral modeling depicts the impact of events. Once preliminary models are created,
they are refined and analyzed to assess their clarity, completeness and consistency. The
analysis start from studying the different systems which also somewhat design on the
concept on which are working. The number of reference we searched to let us understand
the concepts and what we really needed to developed. There are number of meetings we
attend to get the exact requirement for this system.

4.2 OVERVIEW OF THE APMS

Management remains a very necessary activity when a large project is going to be built
particularly if it involves a many people working over a relatively long time. Project
management is a process of planning, organizing and managing the tasks and resources
to accomplish the defined objective, usually within limitations on time, resources or cost.
A project plan can be simple, for example, a list of tasks and their start and finish dates
written on notepad. Or it can be complex, for example thousands of interdependent tasks
and resources with a million-dollar budget.
Whether simple or complex, however all project consist of following major phases:
1) Define the project
2) Build the Milestones
3) Monitor the Project plan
4) Control the project activities
5) Commit the project activities
6) Finalizing the project

CICA\MCA\PRJ29 - 22 - ACE Associates

INTRODUCTION THE PROJECT CHAPTER 1

The more successful these phases are, the greater your chance of a successful project.

4.3 Existing System Study

Organization usually involves into number of projects and each projects are involve
number of employee. There might be possible that one employee has the different project
role on one project and different project role on second project. The concept is represented
into the following figure.

Organization

Projects

Departments

Employee

Figure 4.1 Project and People division in existing system

4.3.1 Project Assignment

Organization contains the number of different project which are usually having very long
time schedule. Project’s work is assigned to the different departments of organization.
Each department has department head that is responsible for the assignment submitted
into his department. Again the department’s work is given to the different employee
working in that department who is only responsible for his work submitted to him. This is
the project assignment configuration into the organization. Now once the project
assignment completes or during the project assignment there are some different role
comes into the picture which shown in the figure name is people hierarchy.

CICA\MCA\PRJ29 - 23 - ACE Associates

INTRODUCTION THE PROJECT CHAPTER 1

4.3.2 People hierarchy

People hierarchy is the level of different project role of employee on the different projects.
The description of each role is as follows:
Administrator: is able to access all the projects and all its phases running into the
organizations and is at the top of the project role.
Project Leader: is able to access only the projects on which are assigning as the project
leader and all that project phases. He can be restricted by the system
administrator.
Department Head: is able to access all the assignment submitted into his department
which are belongs to the different projects.
Employee: is only the responsible for the task assign to him which is belongs to any
department assignments.

Projects

Project Milestones

Dept. Assignments

Emp. Assignments

Figure 4.2 Project distributions in existing system

4.3.3 Project Distribution

Projects which are submitted into organization are divided into the different phases and
each phases is assign to specific employee who is only responsible for that phases and
even also responsible for the phases which belongs to that phases. The description of each
phase is as follows.

Project Milestones: To achieve the project successfully the organization will divide the
project into the project milestone. Project milestone is not assigned to employee
or to the department. It is the small module of the whole projects. Project leader
of this project and system administrator is responsible for this activity.
Department Assignment: Once the milestone is defined it is partitioned into different
department tasks and submitted into the departments. Project leader, system

CICA\MCA\PRJ29 - 24 - ACE Associates

INTRODUCTION THE PROJECT CHAPTER 1

administrator is responsible for this activity. Each department assignments are

associated with the department manager.

Employee Assignment: Department assignment’s again partitioned into employee

assignment which is finally assigning to the employee. Team leader, department
head, project leader, system administrator is responsible for this activity.

4.4 COMPLEXITY WITH THE EXISTENCE

In any of the organization, the project managers usually have difficulties in the following
activities of the project management.
1. Project planning and distribution
2. Co ordination and communication

Project planning and distribution: In organization there are numbers of project running
simultaneously. Consider at least 10 projects are running simultaneously. There are
numbers of department are there in a company. Each department involve in different
project for a specific phase of project. Some of the departments are working
simultaneously on a project work some of them are dependently work on the project. In
departments there are number of employee working on the project, they are may be
independently work or may be in team work.

So that it would be very complex to plan and manage the project especially when many
peoples are involve in the long time project. One shall always have to manually
communicate with his senior for his completion or incompletion task. This case might
humiliate the whole project work if it would not manage correctly.

Coordination and Communication: There may be possible that employee require

leaving the project because of some reason. The employee must be replaced by the other
employee because the projects need to be complete in time. How did the project leader
will search the other employee preferable to that project? The project leader has to search
the organization record and shall fill the employee gap. This would take very long time to
coordinate the resources.

Another thing is that usually in long time project, the project team member has to go out
from the organization for the project work. How he will communicate with the people who
are at the long distance and require the reports from each other. This would be difficult if

CICA\MCA\PRJ29 - 25 - ACE Associates

INTRODUCTION THE PROJECT CHAPTER 1

they are using Existing E-mail services because team member are dynamically change
during the different projects.

So that to engulf this problems, let we have centralized control, centralized monitor on a
different project to resolve the above problem during the project development session.
 Let the system plan and distribute the project milestones.
 Let the system control the changes occur in the project tasks and project activities.
 Let the system bridge the communication gap during the whole project
development session.

4.5 REQUIREMENTS OF NEW SYSTEM

4.5.1 Requirement Collection and Analysis

Requirement collection is the processes of finding the actual context on which we

shall be proceed to design and develop the software application. We achieved this
target by doing some the activities like meeting with the experts; reviewing the
requirements, internet surfing, number of books reading.

Consult with the users: To understand the specific requirement of organization and users
few employees or organization were interview may times. This interview resulted in user
specific and view point oriented requirements. At the first time we interviewed Mr. Nikhil
koringa who is the owner of the Organization and Mr. Vasudev Sheta who is the end use
cum external guide.

Internet: During the analysis we surfed many web sites, to collect the information about
the Architectural project management, but there is no any useful link after all spending
more times we find some of the link which will give the idea of how actual project can be
managed?

4.5.2 Requirements Artifacts

In the software requirement specification, we have used the following attributes to

develop the requirements metrics. The next two tables gives the detailed description of
each attributes.

4.5.2.1 Attributes

CICA\MCA\PRJ29 - 26 - ACE Associates

INTRODUCTION THE PROJECT CHAPTER 1

Attributes Description List Values

Priority A feature’s priority is set by the marketing, the High
product manager or the business analyst. The
priority attributes is designate the relative
Medium
importance of implementing a feature. This attribute
is used in managing scope and determining
development priority. Low

Stability A feature’s stability is set by the analyst and High

development team, and is based on the probability
that the feature will change or that the team’s
Medium
understanding of the feature will change. This
attribute is used to help establish development
Low
priorities and determine those items for which
additional elicitation is the appropriate next action.

4.5.2.2 List Values

Value For Attributes Description

High Priority Critical to the success / survival of the business or a
direct order from the investor or a key account.
Medium Priority Advantageous – adds competitive edge – a unique
feature.
Normal Priority Possible, not necessarily advantageous.
Won’t Priority Nor worth the effort.
High Stability Will most likely change, or is so vague as to need
further elaboration before work can begin.
Medium Stability May change, but is stable enough to begin work.
Low Stability Will almost certainly not change – should be
satisfied early in our process.

CICA\MCA\PRJ29 - 27 - ACE Associates

INTRODUCTION THE PROJECT CHAPTER 1

4.5.3 Requirement Specification

Req. ID Requirement Name Priority Stability

SRS1 Functional Requirement
SRS1.1 Employee details and Maintenances
1.1.1 The system should display employee information High High
in separate form.
1.1.1.1 Name High High
1.1.1.2 Address High High
1.1.1.3 Phone Medium Medium
1.1.1.4 Employee ID Medium Medium
1.1.1.5 Mobile No Medium Medium
1.1.1.6 Designation High High
1.1.1.7 Joining Date High High
1.1.1.8 Department High High
1.1.1.9 Current Working project High High
1.1.1.10 Sex Low Low
1.1.2 The system shall display the employee High High
information about the specific project
1.1.2.1 Project Joining Date High High
1.1.2.2 Project Leader High High
1.1.2.3 Employee ID High High
1.1.2.4 Project Responsibilities High High
1.1.2.5 Points High High
1.1.3 The system shall update employee information High High
any time.
1.1.4 The system shall delete the employee from Low High
database.
1.1.5 The system shall update the employee High High
information about the specific project.
1.1.5.1 Project leaving date High Medium
1.1.5.2 Points High Medium
1.1.5.3 Responsibilities. High High
1.1.5.4 The system shall allow the project leader to assign High High
the points to employee on particular project as per
his performance.

CICA\MCA\PRJ29 - 28 - ACE Associates

INTRODUCTION THE PROJECT CHAPTER 1

Req. ID Requirement Name Priority Stability

SRS 1.2 Department Details and Maintenances. High
1.2.1 The system shall list all department information in High High
separate form.
1.2.1.1 Department Name High High
1.2.1.2 Current Working Project High High
1.2.1.3 Total Employee Low Low
1.2.1.4 Department Head High High
1.2.2 The system shall view the department information High Low
about the specific project.
1.2.2.1 Project Assign date. High Low
1.2.2.2 Completion date High Low
1.2.2.3 Project Leader High Low
1.2.2.4 Total Employee High Low
1.2.2.5 Project Tasks High Low
1.2.3 The system shall update the department High High
information any time.
1.2.4 The system shall update the department High High
information about the specific project.
1.2.4.1 Project Completion date High High
1.2.4.2 Project Leader High High
1.2.4.3 Project Tasks. High High
1.2.5 The system shall enter the new department. High High
1.2.6 The system shall facilitate to assign the High Low
department head for specific project.
1.2.7 The system shall allow storing the reason for High High
deleting department from the organization.
SRS 1.3 Project Details and Maintenances High
1.3.1 The system shall view the entire running project High High
in the separate view form.
1.3.1.1 Project Name High High
1.3.1.2 Starting Date High High
1.3.1.3 Approximately Ending Date High High
1.3.1.4 Project Status Medium Medium
1.3.1.5 Project Leader Medium High

CICA\MCA\PRJ29 - 29 - ACE Associates

INTRODUCTION THE PROJECT CHAPTER 1

Req. ID Requirement Name Priority Stability

1.3.2 The system shall view the information about the High Medium
particular project.
1.3.2.1 Starting date High Medium
1.3.2.2 Departments High Medium
1.3.2.3 Completion date High Medium
1.3.2.4 Approximately Ending date High Medium
1.3.2.5 Status High Medium
1.3.2.6 Project Milestones High Medium
1.3.2.7 Project Leader High Medium
1.3.3 The system shall update the information about the High High
project
1.3.3.1 Entered new Department Low High
1.3.3.2 Enter/Delete Employee High High
1.3.3.3 Extends the completion date High High
1.3.3.4 Approximately Ending Date High High
1.3.3.5 Project Milestones High High
1.3.3.6 Project Leader. Medium High
1.3.4 The system shall enter the new project High High
information.
1.3.4.1 Project name High High
1.3.4.2 Project Code High High
1.3.4.3 Project Description High High
1.3.4.4 Project Tasks High High
1.3.4.5 Starting date High High
1.3.4.6 Departments High High
1.3.5 The system shall finalize the project when it has High High
been completed or rejected.
1.3.5.1 Completion Date/Finished Date High High
1.3.5.2 Status High High
1.3.6 The system shall allow the responsible user to High Medium
change the employee who is currently working on
the project.
1.3.7 The system shall allow the user to go to a High Low
particular project milestones detail from the
particular project information on the form.
Req. ID Requirement Name Priority Stability

CICA\MCA\PRJ29 - 30 - ACE Associates

INTRODUCTION THE PROJECT CHAPTER 1

SRS 1.4 Project Distribution and Maintenances

1.4.1 The system shall allow the user to divide the High High
project into the project milestones.
1.4.1.1 Milestone Name High High
1.4.1.2 Starting date High High
1.4.1.3 Approximately Achieve Date High High
1.4.2 The system shall allow the user to divide the High High
project milestones into the department tasks.
1.4.2.1 Department task Name High High
1.4.2.2 Starting date High High
1.4.2.3 Approximately ending Date High High
1.4.2.4 Task dependencies Low High
1.4.3 The system shall allow the user to divide the High High
department tasks into the different employee
tasks.
1.4.3.1 Employee task Name High High
1.4.3.2 Deadline High High
1.4.3.3 Dependencies Low High
1.4.5 The system shall allow the administrator to assign High High
or update the department tasks to different
department.
1.4.6 The system shall facilitate to assign the project High High
leader for specific project.
1.4.6.1 Joining Date High High
1.4.7 The system shall facilitate to assign the High Medium
Department manager on specific department
task.
1.4.8 The system shall allow the project leader to High High
extend the completion date of following.
1.4.8.1 Department Tasks High High
1.4.8.2 Employee Tasks High High
1.4.9 The project leader/Department Manager can High Medium
stores the reason for extending the date of project
work.
1.4.10 The system shall allow storing the reason for Medium High
deleting the employee from particular task.
Req. ID Requirement Name Priority Stability

CICA\MCA\PRJ29 - 31 - ACE Associates

INTRODUCTION THE PROJECT CHAPTER 1

1.4.11 The system shall allow storing the reason for Medium High
deleting the department task.
1.4.12 The system shall record the rollback information High High
about the department as well as employee and
store the following information.
1.4.12.1 New Completion date High High
1.4.12.2 Reason for roll backing High High
1.4.12.3 Rollback by Medium Medium
SRS 1.5 Monthly target reporting and assignment
1.5.1 The system shall view the monthly targets to Medium High
specific department.
1.5.2 The system shall view the monthly targets to High High
specific employee.
1.5.3 The system shall generate the monthly task report Medium High
of department as well as employee with the
following details.
1.5.3.1 Task name Medium High
1.5.3.2 Starting date Medium High
1.5.3.3 Completion date Medium High
1.5.3.4 Extended Date Medium High
SRS 1.6 Quarterly Target assignment and reporting
1.6.1 The system shall view the quarterly target to High High
specific department.
1.6.2 The system shall view the quarterly target of a High High
specific employee.
1.6.3 The system shall generate the quarterly task Medium High
report of a particular department as well as the
employee with the following details.
1.6.3.1 Task Name Medium High
1.6.3.2 Starting date Medium High
1.6.3.3 Completion Date Medium High
1.6.3.4 Extended Date Medium High
SRS 1.7 Messaging Services
1.7.1 The system shall allow the project leader, Medium Medium
employee to pass the message of different type.
1.7.2 The message can of the following Medium Medium
Req. ID Requirement Name Priority Stability

CICA\MCA\PRJ29 - 32 - ACE Associates

INTRODUCTION THE PROJECT CHAPTER 1

1.7.2.1 Reminder Medium Medium

1.7.2.2 Urgent Medium Medium
1.7.2.3 Notification Medium Medium
1.7.2.4 Regular Message Medium Medium
1.7.3 The system shall generate the message High High
automatically when project completion date is
exist.
1.7.4 The system shall generate the notification High High
message and send to employee and his senior
when the task finishing date is exists.
1.7.5 The system shall allow the employee to send the Medium High
request to project leader to extend the task
completion date.
1.7.6 Delete the Message Medium High
1.7.7 The system shall allow the message to user when High High
try to delete unread message.
1.7.8 The system shall protect the emergency message High High
from deletion by user.
1.7.9 The system shall allow the user to send the High Low
message more then one user at a time.
1.7.10 The system shall have the automatic messaging High Medium
services with the following events.
1.7.10.1 When new project entry is entered project leader High Medium
shall have the notification message
1.7.10.2 When the project milestone is created the High Medium
administrator and the involve department shall
have the notification message.
1.7.10.3 When the project milestone is divided into the High Medium
department task each department shall have the
notification message.
1.7.10.4 When the department task is divided into the High Medium
employees work each involve department shall
have the notification message.
1.7.10.5 When the department task is rollback for the new High Medium
completion date the department head shall have
the notification message.
Req. ID Requirement Name Priority Stability

CICA\MCA\PRJ29 - 33 - ACE Associates

INTRODUCTION THE PROJECT CHAPTER 1

1.7.10.6 When the employee task is rollback for the new High Medium
completion date the project leader shall have the
notification message
1.7.10.7 When the employee is requested for extending the High Medium
completion date the message shall be forward to
department head, project leader, and Manager.
1.7.10.8 When the employee is removed from a particular High Medium
task by the department head, the message shall
be forward to project leader as well as
Department head.
1.7.10.9 When the project Milestone is changed by the High Medium
project leader the message shall be sent to
administrator.
1.7.10.10 Project milestone date has been exited, the High Medium
message shall be sent to admin.
1.7.10.11 When the evolution point is given to the High Medium
employee, the employee shall receive the
message.
SRS 1.8 Meeting declaration and Maintenance
1.8.1 The system shall allow the project leader to Low Medium
arrange the meeting on specific project
1.8.2 Project leader to involve the specific employee for Low Medium
the meeting.
1.8.3 The system shall automatically send the message Low Medium
about the meeting to the selected employee.
1.8.4 Topics/Reason to be discusses in the meeting. Low Medium
1.8.5 The system shall allow the user to enter the Low Medium
following attributes of the meeting.
1.8.5.1 Project Name Low Medium
1.8.5.2 Meeting Date Low Medium
1.8.5.3 Minutes of Meeting Low Medium
1.8.5.4 Results of Meeting Low Medium
1.8.5.5 Next Meeting Low Medium
1.8.6 The system shall allow change/update the Low Medium
meeting information.
Req. ID Requirement Name Priority Stability
1.8.6.1 Project name Low Medium

CICA\MCA\PRJ29 - 34 - ACE Associates

INTRODUCTION THE PROJECT CHAPTER 1

1.8.6.2 Meeting date Low Medium

1.8.6.3 Topics Low Medium
1.8.6.4 Meeting Results Low Medium
1.8.7 The system shall keeps record of each meeting Low Medium
details.
1.8.8 The system shall view monthly information of Low Medium
meetings.
1.8.8.1 Project name Low Medium
1.8.8.2 Meeting date Low Medium
1.8.8.3 Hours of Meeting Low Medium
1.8.8.4 Results of Meeting Low Medium
1.8.9 The system shall facilitate the user to recreate the Low Medium
same meeting if the conclusion shall not be
achieved from the first meeting
SRS 1.9 Report Generation High High
1.9.1 The system shall generate report of currently High High
running projects information.
1.9.1.1 Project Name High High
1.9.1.2 Project Leader High High
1.9.1.3 Project Code High High
1.9.1.4 Project Starting date High High
1.9.1.5 Project Completion date High High
1.9.1.6 Project Description High High
1.9.1.7 Project total Meeting High High
1.9.1.8 Involve department High High
1.9.2 The system shall generate the report of completed High High
project
1.9.2.1 Project Name High High
1.9.2.2 Project Leader High High
1.9.2.3 Project Code High High
1.9.2.4 Project Starting date High High
1.9.2.5 Project Completion date High High
1.9.2.6 Project Description High High
1.9.3 The system shall Generate the report of monthly High Medium
completed task.
Req. ID Requirement Name Priority Stability

CICA\MCA\PRJ29 - 35 - ACE Associates

INTRODUCTION THE PROJECT CHAPTER 1

1.9.4 The system shall Generate the report of quarterly High Medium
completed task.
1.9.5 The system shall generate the report of whole the High Medium
project task from starting to completed specific
date.
1.9.6 The system shall generate the whole project High Low
activities report.
1.9.6.1 Project name High Low
1.9.6.2 Project ID High Low
1.9.6.3 Department Name High Low
1.9.6.4 Employee List and responsibilities High Low
1.9.6.5 Total Days High Low
1.9.6.6 Tasks Details High Low
1.9.6.7 Meeting Details High Low
SRS 1.10 Evolution Medium
1.10.1 The system shall allow the project leader to Medium High
administrator to give the rank to employee
according to their observation of employee on
particular project.
1.10.2 The system shall allow project leader or Medium High
administrator to view the evolution history of
employee during the task assignment.
1.10.3 The system shall have the facilities to change the Medium High
evolution rank anytime during the project
development.
SRS 2 USER INTERFACE REQUIREMENTS
SRS 2.1 Basic form Designing requirements High High
2.1.1 Form shall have the menu driven facility. Low Low
2.1.2 Forms can’t be highlighted with dark or fast colors. Low Low
2.1.3 The forms shall have the window application Low Low
looks.
2.1.4 The information on the form shall be displayed in Medium Medium
the grid layout.
SRS 2.2 Read and unread messages shall be Discriminate High High
graphically
Req. ID Requirement Name Priority Stability

CICA\MCA\PRJ29 - 36 - ACE Associates

INTRODUCTION THE PROJECT CHAPTER 1

SRS 2.3 The extended date should be identified having the High High
different color.
SRS 2.4 The report of the project should be generating in Low Medium
the form of chart layout.
SRS 2.5 The attached documentation shall have the Medium Medium
graphical identification.
SRS 2.6 Before the system start user must be login first. High High
SRS 2.7 The application shall generate the message when High High
wrong user has been entered and allow retrying.
SRS 2.8 On successful login the application shall displayed High Low
the project’s name and code according to the
writes assigned to the log user.
SRS 2.9 If message should be come for particular user, High High
then it is notified by the Status bar icon.
SRS 2.10 The type of message shall be displayed. High High
SRS 2.11 On line help must be provided for some important High High
forms control.
SRS 2.12 The project list form shall display the following High High
information about the project.
2.12.1 Project Code High High
2.12.2 Project leader High High
2.12.3 Involve Department High High
2.12.4 Starting date High High
2.12.5 Ending Date High High
SRS 2.13 Once the project has been completed it should be High Medium
automatically removed from the list.
SRS 2.14 The application shall have the option for the High High
viewing the previous completed/rejected project.
SRS 3 Project Money Payable And Receivables High
3.1 The system should maintain the overall project High Medium
Money Payable And Receivables.
3.1.1 Agencies Name High Medium
3.1.2 Code High Medium
3.1.3 Project Code High Medium
3.1.4 Voucher No. High Medium
3.1.5 Price High Medium
Req. ID Requirement Name Priority Stability

CICA\MCA\PRJ29 - 37 - ACE Associates

INTRODUCTION THE PROJECT CHAPTER 1

3.1.6 Ordered Date High Medium

3.2 The system should maintain the payment detail High High
for particular project.
3.2.1 Project Code High High
3..2.2 Agencies Name High High
3.2.3 Code High High
3.2.4 Final amount High High
3.2.5 Voucher No. High High
3.2.6 Payment type. High High
3.2.7 Bank High High
3.2.8 Date High High
3.3 The system should maintain the incoming High High
payment from the client for particular project.
3.3.1 Project code High High
3.3.2 Client Name High High
3.3.3 Date High High
3.3.4 Payment type High High
3.3.5 Amount High High
3.3.6 Bank Name High High
SRS 4 Backup of Project Data. High
4.1 The system should maintain information about the High High
old project data is resides in which CD no.
4.1.1 Year of Backup High High
4.1.2 Stage High High
4.1.3 CD No. High High
4.1.4 Project Code High High
4.1.5 Client Name High High
4.1.6 City High High
4.1.7 Project Type High High
4.1.8 Date of Backup. High High
4.2 The system should also maintain the information High High
about the total drawing detail for the particular
project at Backup Time.
4.2.1 Key Code (year+stage+cd_no+pro_code) High High
4.2.2 File Name High High
4.2.3 Type High High
Req. ID Requirement Name Priority Stability

CICA\MCA\PRJ29 - 38 - ACE Associates

INTRODUCTION THE PROJECT CHAPTER 1

4.2.4 Size High High

4.2.5 Date of Last modification High High
SRS 5 Non-Functional Requirement
SRS 5.1 Security Requirement High
5.1.1 The password shall be stored in encrypted form Low Medium
5.1.2 There system shall have the utilities through High High
which the responsible person can assign the
writes to specific task assign to him.
5.1.3 Employees should not be able to extend the High High
completion date of the specific task assign to him.
5.1.4 The login must be starting of the application. High High
5.1.5 From one machine or computer system only one High High
user shall access the system.
5.1.6 There is project leader of department head who High High
has assigned all the writes for the different
project.
5.1.7 The system shall display only those projects in High High
which the currently logged on user is involve.
5.1.8 According to the role of employee following screen High High
layout shall displayed on screen.
5.1.8.1 If logon user is Project Leader or Department High High
Head, then the following list shall be displayed.
5.1.8.1.1 All completed projects code. High High
5.1.8.1.2 Project Leader High High
5.1.8.1.3 Starting Date High High
5.1.8.1.4 Ending Date High High
5.1.8.1.5 Involve Department High High

CICA\MCA\PRJ29 - 39 - ACE Associates

INTRODUCTION THE PROJECT CHAPTER 1

Req. ID Requirement Name Priority Stability

SRS 6.0 Other Requirements High
6.1 The password shall have maximum of 15 High Medium
character abs minimum have 5 characters
6.2 Reason for the following events shall not exceed High Medium
more then 200 characters.
6.2.1 Employee is leaving the project High Medium
6.2.2 Rolling the department’s tasks. High Medium
6.2.3 Rolling the Employee’s task. High Medium
6.2.4 Meeting Arrangement High Medium
6.2.5 Change the project leader High Medium
6.2.6 Change the Department Leader. High Medium
6.2.7 Deleting the project High Medium
6.2.8 Discarding the project. High Medium
6.2.9 Evolution point assignment High Medium
6.2.10 Removing the project milestones High Medium
6.2.11 Deletion the Department High Medium
6.3 Task name shall not exceed more then 100 High Medium
characters.
6.4 Meeting conclusion shall not be exceeding more High Medium
then 200 characters.
6.5 Project code shall have 9 characters. High Medium
6.6 All descriptive fields shall not be exceeding the High Medium
limit of the 150 characters.

CICA\MCA\PRJ29 - 40 - ACE Associates

INTRODUCTION THE PROJECT CHAPTER 1

4.6 FUNCTIONAL MODELING

The functional modeling shows how values are computed without regard for sequencing,
decisions, and object structure.
The functional model shows which values depends on which other values and the functions
that relate them. The Functional decomposition diagram describes how the whole systems
are divided in to the sub systems and their hierarchy in the system.
Dataflow diagram are useful for the showing functional dependencies. Functions are
expressed in various ways, including natural language, mathematical equations and
pseudo code.

The processed on a data flow diagram corresponds to activate or actions in the state
diagrams of the class. The flow on a data flow diagram corresponds to the object or
attributes values in an object diagram.

The functional decomposition diagram of the system are given below

CICA\MCA\PRJ29 - 41 - ACE Associates