Introduction *

9, Software products go tl~rvugh several

stages as they rrlature froitr~initial concept
ty finished prodi~ct
+ he' sequence of stages is called a life
cycle
-+It is irrrpcartantt to design and document
software in an anrganizetl way so that it
can be easily understood and maintained
after the initial release
i;p The person who maintains the, software is
not necessarily t h person
~ who writes it
 ---
s requirements

One of the first ! j t ~ p s is lo gather the right

requirements. This is done in a varioty at' ways based
on the methodology that the company employs. It is
a complex process and involves a period:

1 Discovery and Education,

2. Formal communication,
3. Reviews
4. Final approvals.

Requirements
-+Business requirements are gathered in
this phase
.) This phase is the rnain focus of the project
managers and stake holders.
.$ Wlho is going to use thc; system?
+ Haw will they use the systern?
1) What data should be input into the
system?
+What data should be output by t h e
system?
 Design

+software system design is produced

$ architecture
+ including hardware and software
T) corrrrnunication
-+ software design

Implementation

+ Code is protluced
$this is the longest phase of the
,

software development life cycle

4 lmplementation my overlap with both
the design and testing phases
+For a developer, this is the main
focus of the life cycle
+Once the new system is up and
running for a while, it is
exhaustively evaluated.
.rl, Maintenance is kept UP
rigorously at all times.
+Users of the system are kept
up-to-date concerning the latest
modifications and procedures.

Entities in -asystem ---

d Retained Entities

.$ Transient Entities
 Evaluation of System Requests

+ Systems Re\tiew Committees

I
+ Evaluation of projects
4Feasibility study
8t Operational Feasibility
RTecknical Feasibility
$4 Economic f~!asibility
8 Cast-benefit analysis

Systerr~Planning Preliminary Investigation report

B Syslel'rl Analysis -- System Requiten~ent
Specifications
4 Systarn Design -- I;ystems Design Specifications
r~ Systern Development - Proyramming & Testing
a Systern Implementation -. Carnplete Functioning
Systerx1
4 Systerri 0peratior.1~and Support - Freedback and
fine-lunirig
4 Systern Evaluation -- Redesign or' A C G B P ~

Pt is itera five
T) FINAL OUTPUT IS : FEASIBtLITY
S"rWDY REPORT t4AVING

FINANCIAL f=EASIBILITY
ECONOMIC VIABILITY
TECHNICAL FEASIBILITY
SOCIAL FEA,SIBILITY

REQUIREhAENTS ANALYSIS -

.B INVESTIGATION 13r ANLYSIS :

Et Collectlorl d ~nforrnatrorlabout llic existing systerrr

Ids11tificnt1onof d~tflculties,prot:l~?rnsK bottlsnt?cks 11)
the c:xlsting systt?rn
# Ide~itilic;?tionof rcquirc:ments of the new systtm
 .-

SYSTEM DEVELOPMENT
+ PROGIRAMMINGAND TESTING :
WRITE ACTUAL PROGRAMS TO t-fANQLE THE
SYSTEM DATA
* PROGWMMING SKIL.LS AND EXPERIENCE IS
FEQUIRED FOR THIS PI-dASE
* SIMPLE CLEARLY DEFINED PROGRAM M 0 0 t J I - E S
WILL ME EASIER r 0 TEST INDEPENDENTL\( AND
AL..C)NGWfTEI OTHER MODULES

-.

--

Program Testing -

$ Syrltax Errors
4 Semantics
+ Desk C heckingJWalkthrus
$ CodeJDesign Walkthrus
 PI

SYSTEM DEVELOPMENT -
+ ACTIVITIES INVOLVED IN PROGRAMMING &
$8 Check program specifications
# Breakdowr~ pr0gram.s and modules, allocate to
prograrnrrlers
$4 F3mducccode in choson language
E Uefin~,module and link tests
&tEnsure data availability for integration testing
$? Check quality of code
E Document a11 Programs
R Ensure t~3arprovides ~cchf)tance test data
a3 Cornplefe ~ntegration testing
Complete acceptance testing
Pt sign-off .S;"ystems;as meeting user sp@c~fication
 System Training -
+ For IT Staff
$SMaintenance !Staff
Operations Staff
W Job Cantrnl Staff
9System Users
+ Marwigers
a Various Training Alternatives Used
* Vendor Training
Trairiiny hsaurcos
e>t.~tside
- a In-house Tra~ning

Training the IT Staff -

4 Project History and Justification

4 System 'Architecture
P, System Docun"rr~tation
. b ~Typic:al User Questions
4 vendor Support
Lagging and R,esolving Probleu~s
+ Technical Trainir~gfor It Staff
$ LJssr and Management Training
 Data Conversion -
+ Data conversion plan is a k~ust
9 Exparting from old systems
ASCII or ODBC(0pen Data Base Ccrnnsclivity)
are standard formats
4 Else we may need to write to Data Cor~version
programs
-4 Strict Input Control - Users may be nsaded to
verify data
+ During this phase, data cleanup may also be a

needed

System Changeover -

+Put the new system in place and

retire the old system
8 Direct Cutover - Just repiace
$4 Parallel Operation - OldINew operate
simultaneo~~sly
8 FFilot Operation lrr~plemerrt at a
selected location and then move further
@Phased Changeover -- Irnplt3ment in
stages, wraclules, subsyskms
 General Life Cycle Model

R,equirements Vs. Delivery

I What user wanted How curtorner d6$scnlradit Now analyst apscithed il ktuw designer ~n~plcmanted
~t
 Requirements (Cont...)
a This produces a r~ice big list of
functionality that the system should
provide
lp Which describes functions the systern
should perform
+ Business logic: that processes data
9 What data .is stored and used by the
system
+ How the user interface should work.

Planning
The plans are laid out concerning the:
4 physical c~nskruction .
hardware
+ operating systems
-s programming
+ comr-rwnicat ions
 Testing

+ implementation is tested against the

requirements
+ Unit tests and systemlacceptance
tests are done during this phase

Commisioning
+ T h e new system is developed and
t h e new comporlents and programs
are obtained and installed.
Llsers of the system r-r-~ustbe trained
in its use and all aspects of
performance is tested.
+ 1f necessary, adjustments are rnadc
a t this stage.
 The System Analyst --
$ Is a catalyst between tho business and
thp, system teams
a Translates business req~rirernentsinto
practical IT projects
4 As systems develops, he has to perform a
wide set of tasks
Fit Rr-?v#~wmg bu.srnc>ssprocesses
n Selecting hanfwn~c?and snftwt~rt?
t4 Dosigning rnformatronsyslerrts
s I rilinir?~ttsers
at !2/;lnt~rttgfi~turesystetns

Systems Analyst
+ Facilitates the development of
information systems and computer
applications
- he/she performs
- Systerns Analysis
- Syst.erns Design
 System Models
.)Conceptual Model

+ Logical Model
$ Physical Model

SDLC Detailed ----

1 + BREMINIARV.INVES"lf"GATI0N-
' *DEFINE THE PROBL_EM'1 O WE SOLVED
GENERAL DIRECT ION FOR TtiE WHOLE
PROJE(27
~PRQJEC-TBOUNDARIES DEFINED
*tZF!SBUIICES TO L3t: MADE AVAILL\ULE

Final Output : GENERALLY CALLED Terms

of Reference9as set by MANAGEMENT
 . SDLC Detailed ----
+ DESIGN :

a INCI-UEJES MAPPING OF BLJSINESS REQUIREMENTS

OF THE SYSTEM ON 10 THE PROPOSED IU7ESIGN.

LOCICAL DESIGN - defines the usel's outputs, "puts and

promsse~~,
1'1 iYSICAL DESIGN -docs nrilpping of loyto;tl dk!sign an lo Ihe
~vt~rputnrbased ssystetn tn tctnns of I>ATA FILES, t'liO(;KM
MOnlJLES ANbl ~iCII+JPORTINQSOrTtYAME

+ END RESULT IS A DESIGN SPEC>IFIGATIONREPORT

SYSTEM DESIGN --
4 TIESIGN SFJECIFICATI€lN REPORT INCLIJ0F;S :

*T manual system
*T he proposed system
*Sy stem flaw charts
.Module design specificatior~s
.Prinl/Scre!en laycnrt charts
-Data file designs
*P est data specifications
a T E S diita
~ file design
eAcccptarrce test desiy n
+ Unit Testing - Dummy/Actual Data
-+ Integration Testing
+ System Testing
-+ Acceptance Testing

- .-

Documentation -

9 Program Documentation
+ System Documentation
9 Opsratiorrs Documentation
9 her Doct~rnentation

These clays we b~avson-line documentatian

or in-build docun-.lenfation.
I System Implementation

+ Syst,ern Implementation is the

physical level of the system and
results in physical deliverables of the
system
-+Quality control, though it matters
from the first phase onwards, but
assumes more criticality at this
stage.

Installation and Evaluatiorl -

4 So far every activity has been performod in a
Test Environment
&% tfSomc orgar~izutlansalso cnll this .?s a LabIPllot Stla
Envirorirr~ent
Ta Mearrt for It Staff orlly
-J+ Now wo move anta the l~poratiorial or
production environment
u IMcant for lJscrs t~nly
I t rnakes usc of L"~veU u $ i 1 1 6 ? ~ ~Uilta 1r1 p / i l of
~ ~resf
Data wl11ct1is devc?lnpctdas per thc? understanding of
thc It Programmcrs/Stalf
 Training for System Users -

System Overview
4 Key Terms
+ Statt-up and shut dawn
+ Main menu and submenus
+ lcorls and shortcut keys
4 Major system functions
+ On-line and external t~elp
+ FAQs
.) Proubleshuoting guide
1) Handling ernergenties

+ Project orCgin
+ CCast.rBenefit
analysis
+ Support for ~ u s i n e s b ~ o e l s
-+ Key IT contact people
+ Handling Systcni Charges
-II Major reports and tiisplays
+ Requesting Enhancenients
4 User Training
 Post Implemontation Evaluation -

-& To ascertain whether the new system

rneets the requirements.
+ To provide the feedback to the evaluati~n
team
9 Areas to be covered -
8 Accuracy, cumpletedness, and timelinass c?f
the system output .
$3 User satisfaction
# Systcm reliability and maintainability

System controls and security measures

tiardwaro cfficic.ncyand y latforrn per-formance
# Effectiveness of database irnplc~rnenbation
W Perfnrrnance of ths IT team
# Cosnploteriess and quality of dacurnentation
$4 Quality and efft:ctivencss of training
Ft Accuracy of CB Analysis
9 Who sttould conduct the evaluation and
wtlen?