c






 

  







 For Problem Analysis phase, the inputs are problem statement and scope & vision to this phase and
the output from this phase is system improvement objectives.

 
 


Input: System Improvement Objectives
Output: Business Requirement Statement

 


u
 


Input: Business Requirement Statement
Output: Logical Design

  


Input: Logical Design
Output: Physical Design & Prototype

  

 


Input: Physical Design & Prototype
Output: Functional System and Training materials such as User Manuals etc.

 


Input: Operational System, Enhancements
Output: Solution

c
!

 

"
 #
!  


 



 The procedure is called Fast Tracking - Starting successor activities before the completion of their
predecessor activity.

Fast tracking is risky, needs very good coordination and may involve rework. It can be achieved only
incase you have a different set of resources on the predecessor and successor activities also incase of
any free resources you can utilize to do this.

c        

 £. Function Point Analysis

A function point is a unit of measurement to express the amount of business functionality an

information system provides to a user. The cost (in dollars or hours) of a single unit is calculated
from past projects. Function points are the units of measure used by the IFPUG Functional Size
Measurement Method. The IFPUG FSM Method is an ISO recognized software metric to size an
information system based on the functionality that is perceived by the user of the information
system, independent of the technology used to implement the information system. The IFPUG
FSM Method (ISO/IEC 20926 Software Engineering - Function Point Counting Practices Manual) is
one of five currently recognized ISO standards for functionally sizing software.
2. Usecase Points

A use case in software engineering and systems engineering is a description of a potential series of
interactions between a software module and an external agent, which lead the agent towards
something useful.[£ Uses cases are used as a software modeling technique that helps developers
determine which features to implement, and determine how to gracefully resolve errors.

Within systems engineering, use cases are used at a higher level than within software engineering,
often representing missions or stakeholder goals. The detailed requirements may then be captured in
SysML requirement diagrams or similar mechanisms.
SDLC

c
$% 
&

There are 5 phases in SDLC:

£) Requirement & Analysis
2) Design
3) Coding
4) Testing
5) Maintenance

£) Requirement &Analysis: the main aim of requirement analysis phase is to produce a document
that properly specifies all requirements of the customer. Requirement specification document
is the primary output of this phase. Proper requirements and analysis are critical for having
successful project. The need for executing this phase properly to produce an SRS with the least
defect should be evident.
2) Design: during the design phase the user requirements are elicited and software satisfying these
requirements are designed built tested,delivered to the customer.

High level:high level design is the phase of life cycle the logical view of computer implementation of
solution to the customer requirements are developed.it gives the solution at high level of abstraction.
During the high level design the functional architecture of application and database design takes place.
The entry criteria are that SRS has been reviewed and authorized. The input for this phase is software
requirement specification and output for this phase is high level design document. The exit criteria are
that the high level design document has been reviewed and authorized.

Low level design:the view of the application developed in the high level design is broken into modules
and logic design is done for every program .a unit test plan is created and documented as program
specification. The important activity in the detailed design phase is identification of common routines
and programs.

The entry criteria are that the high level design document has been reviewed and authorized. The exit
criteria are that the program specification document has been reviewed and authorized.

Coding:during the coding phase required programing language is used to produce the program.
Thisphase produces source code, executable and database design.

Testing:here actual testing takes place.

Maintenance: successfully developed project will undergo for maintenance

c








There are various SDLC models.

£. Waterfall Model
2. Incremental Model
3. Prototype Model
4. Spiral Model
5. Rapid Application Development Model (RAD)
6. V Model
7. XP Model

c

%



 


Testing starts right from the beginning stage, Requirements Gathering and Analysis.

c






'!




 



('"
( 
 



c




'
 

 



Analysis: It is the process of determining what needs to be done before how it should be done. In order
to accomplish done, the analyst refers the existing systems and documents.

Design: It is the process of adopting/choosing the one among the many, which best accomplishes the
users͛ needs.


c



 
 



'"
  



Objects, Messages, Class, Inheritance and Polymorphism are the main concepts of object orientation.

c




'
)*



'"

SBI stands for State, Behavior and Identity. Since every object has the above three.

State: It is just a value to the attribute of an object at a particular time.

Behavior: It describes the action and their reactions of that object.
Identity: An object has an identity that characterizes its own existence. The identity makes it possible to
distinguish any object in an unambiguous way, and independently from its state.

c



' 


 + 
#



c


 



 
"

!
, 


 '   


 



c
-
 
 
"

c
!





 

A: The current requirement will be analyzed on feasibility point of view that what may happen when a
particular amount of changes will be done in current system and whether it will affect any current
feature or not. If yes then up to, which extent.In general while incorporating changes impact will be
observed by seeing base line effects.

c
!




 

We need to follow following list of process while CR comes up:

£. Feasibility Study
2. Impact Analysis (based on Traceability Matrix if exists)
3. Estimation (will be affected if the client haschances to provide further)
4. Implementation
5. Testing (should be careful about existing functionality)
6. Deployment and Deliverables

c
-



!

 
 . 

c
!
! 


! 

' 


!,


'



 


In this situation,following things must be think and tested

£) Impacted area should get tested

2) Should run all High priority test cases related area where changes have been made.
3) If gets time then run medium priority test cases
4) Do sanity test around the impacted area.

c



 

 
'
 

,!
' 
 
"/

 #  

/

 
 

 

Project Management Plan

c
!


 
,

 

'

Prepare the schedule and assign the resources and share the complete schedule with the stake holders.
This way, team members will be aware of their sequences of tasks and their timelines which will be
tracked on timely basis.

c
!


 







'

 
"
#

 

 
, 

% 

"