 Understand what is Systems Development.

 Identify who are involved in Systems

Development
 Understand each phase in Systems
Development Life Cycle (SDLC).
A conceptual model used in Project Management
that describes the stages involved in an
information system development project, from an
initial feasibility study through maintenance of the
complete application.

A SET OF ACTIVITIES USED TO BUILD AN

INFORMATION SYSTEM
 System Developer

 System Analyst

 System Designer
"Being a system developer means you need to
learn to listen and clarify requirements,
interpret them and deliver fit for purpose
solutions even if your stakeholders don’t
originally know what they want. You must also
anticipate future demands, and ensure you
stay on top of all the latest hardware and
software developments." Paul Cussell, RS
Consulting
 Tasks vary according to the type of organization and
size of employer but may typically involve:
◦ analyzing user requirements;
◦ researching, designing and writing new software programs;
◦ testing new programs and fault finding;
◦ evaluating the software and systems that make computers and
hardware work;
◦ developing existing programs by analysing and identifying
areas for modification;
◦ integrating existing software products and getting
incompatible platforms to work together;
◦ creating technical specifications and test plans;
◦ writing and testing code and then refining and rewriting as
necessary;
◦ writing systems to control the scheduling of jobs on a
mainframe computer or to control the access allowed to
users or remote systems;
◦ writing operational documentation with technical authors;
◦ maintaining systems by monitoring and correcting software
defects;
◦ working closely with other staff, such as project managers,
graphic artists, designers, developers, systems analysts, and
sales and marketing professionals;
◦ consulting clients/colleagues concerning the maintenance
and performance of software systems and with a view to
writing or modifying current operating systems;
◦ investigating new technologies;
◦ continually updating technical knowledge and skills by
attending in-house and/or external courses, reading manuals
and accessing new applications.
 liaising extensively with external or internal clients;
 analysing clients' existing systems;
 translating client requirements into highly specified
project briefs;
 identifying options for potential solutions and
assessing them for both technical and business
suitability;
 drawing up specific proposals for modified or
replacement systems;
 producing project feasibility reports;
 presenting proposals to clients;
 working closely with developers and a variety of end
users to ensure technical compatibility and user
satisfaction;
 ensuring that budgets are adhered to and deadlines
met;
 drawing up a testing schedule for the complete
system;
 overseeing the implementation of a new system;
 planning and working flexibly to a deadline;
 writing user manuals;
 providing training to users of a new system;
 keeping up to date with technical and industry
developments.
 Nothing is more difficult than creating a system out
of thin air.

 A model is just a simplified representation of reality

and can take many forms.

 You can have data without operations but you can't

have operations without data.
 Need to know existing flow of works
 Need to find out all the reports that have
been produced
 Need to find out the origin of information
 Need to know why the need of new system –
find out the problem of existing system
 To see which existing processes should be
handled by computer and which should be
done by non computerized methods
 Determining what changes should be made
 Determining how best to solve an information
systems problem
 System analysis only
 System analysis and design
 System analysis, design and programming
 work with analysts on the feasibility of a conceptual
design by taking technical specifications prepared by
the analyst and designing system components to
meet the set requirements
 draw up detailed design documentation including
charts and diagrams that indicate the various
components involved
 A user may request a new or modified system
 Organizations may want to improve hardware,
software, or other technology
 Situations beyond an organization’s control might
require a change
 Management might mandate a change
 A user may request a new or modified information
system using a request for a system services or a
project request
 The systems development life cycle (SDLC) is
a conceptual model that describes the stages
involved in an information system
development project, from an initial
feasibility study through maintenance of the
completed application.
 Is a set of steps that serves as the basis for
most systems analysis and design
methodologies
 Waterfall
 Rapid Application Development (RAD)
 Joint Application Development (JAD)
 Fountain model
 Spiral model
 Build and Fix;
 Synchronize-and-stabilize.
1. Waterfall
◦ the classic approach
◦ describes a development method that is linear and
sequential.
 The advantages:
◦ allows for departmentalization and managerial control
◦ A schedule can be set with deadlines for each stage of
development
◦ Each phase of development proceeds in strict order,
without any overlapping or iterative steps
 The disadvantages:
◦ not allow for much reflection or revision.
 Involved scheduling and then
controlling of activities during system
development
 Must identify:
◦ Project scope
◦ Required activities
◦ Time estimates for each activity
◦ Cost estimates for each activity
◦ Order of activities – e.g. Activities that can take
place at the same time
Develop the project plan including tasks, resources,
and timeframes
 Project plan - defines the what, when, and who
questions of system development
 Project manager - an individual who is an expert in
project planning and management, defines and
develops the project plan and tracks the plan to
ensure all key project milestones are completed on
time
 Project milestones - represent key dates for which
you need a certain group of activities performed

6-32
 Begins when the steering committee receives
a project request

 4 main activities
◦ Review and approve the project requests
◦ Prioritize the project requests
◦ Allocate resource
◦ Form a project development team
Planning Works Activity Description

A)Schedule 1. Define Activities identification of the

Management Plan specific work activities
that need to be performed
to complete the project

2. Sequence Activities Identify and document the

logical relationships
among schedule
activities.

3. Estimate Activity Estimation of the type and

Resources quantities of resources
required to complete
identified activities.
Planning Activity Description
Works

4. Estimate Activity Estimation of the approximate

Durations duration to complete work packages.
5. Develop Schedule Develop the baseline project
schedule after analysing all defined
activities and work packages,
sequence, resources, and duration.
This section also includes
identification of tools to use for
managing the project schedule.

6. Control Schedule Methods for controlling changes to

the schedule.
Planning Activity Description
Works
B)Cost 1. Estimate development of a complete estimate of the
Management Costs funding needed to complete project
Plan activities, including operations, maintenance,
and support costs for the life of the project

2. Determine combination of work package costs to

Budget establish an overall budget. Aggregate the
estimated costs of each scheduled activity or
work package, and establish a total cost
performance baseline for measuring project
performance.

3. Control Establishment of procedures to manage the

Costs established cost baseline, so the project is
completed on time and on budget.
Planning Activity Description
Works
C)Quality 1. Plan Verification processes to ensure that the
Management Quality system is successful, that project
Plan stakeholders are satisfied, and that
deliverables are accepted.

2. Perform Procedures for ensuring the

Quality effectiveness of quality management
Assurance processes and quality standards

3. Perform Review activities focused on the quality

Quality of deliverables, including the system, to
Control determine adherence to quality
standards and criteria.
Planning Works Activity Description
D)Staffing By describing how and when
Management Plan human resource requirements
will be met.

E)Communication Describes the detailed

Management Plan processes and techniques the
team will use to collect, store,
and report on project
progress.
 Gather the development Requirement

 Conduct a preliminary investigation

 Perform detailed analysis

 Do the Feasibility study
 A measure of how suitable the development of a
system will be to the organization
◦ Operational feasibility
◦ Schedule feasibility
◦ Technical feasibility
◦ Economic feasibility
 What is being done?
 How is it being done?
 How frequently does it occur?
 How great is the volume of transactions or
decisions?
 How well is the task being performed?
 Does a problem exist?
 If a problem exists, how serious is it?
 If a problem exists, what is the underlying
cause?
1. Preliminary analysis : starting the objectives, defining
nature and scope of problem
2. Propose alternative solution : leave system alone,
make it more efficient, or build a new system
3. Interview the user who submitted the request
4. Submit a preliminary plan with recommendations
– written report
 Review documentation
 Observe
 Survey
 Interview
 Research
• Study how current system works
• Determine the user’s wants, needs and
requirements
• Recommend a solution
• Documentation
 The system proposal assesses the feasibility
of each alternative solution
 The steering committee discusses the
system proposal and decides which
alternative to pursue

Packaged Custom
Outsourcing
software software
 Involves Process Modeling Approach
(structured analysis and design) is an analysis
and design technique that describes processes
that transform inputs into outputs

Entity-
Data flow
relationship
diagrams
diagrams
(DFD)
(ERD)
 Activity
Model

Modeling
(Approaches)
Data Product
Model Model
Activity Model

• Activity model or process model technique has

been used in a number of projects for analysing the information
flow between different information processing activities in the
design and construction.

• This can be represented in an interaction model which shows what

data is required for a certain process.

• The Data Flow Diagram (DFD) is a technique for activity modelling

which shows the input and output of the concerned process and
also a breakdown of each of the main processes.
Activity Model

• The advantage of activity modelling is to simplify

the understanding of the involved processes and
the development of their subsequent applications.

• However, activity modelling cannot be used as a

means to translate conceptual models into physical
databases.
EXAMPLE
EXAMPLE
Data Model

 Data model is a set of concepts that can be used to

describe the structure and operations of a database. The
idea of a data model is to define the behaviour to be
included in a database in response to the complexity of
constructing large database for organisations.

 A data model also provides the basic structuring

mechanisms for describing the data, relationships and
constraints of the information stored in any information
system. Using a specific data model, conceptual models
can be built.
EXAMPLE
make is referred by Concrete
Costumer
Specification
-Customer ID -Specification ID
-Customer Name -Aggregate ratio
-Customer Phone No -Sand ratio
-Customer Address is made by refer -Cement ratio
-Person In charge -Order Number -Water ratio
-Customer ID refer
-Specification ID Order
-Quantity is referred by
-Strength
check
-Delivery Date

is checked by is checked by is checked by is checked by

Aggregate Sand Cement Water

-Order Number add to -Order Number add to -Order Number add to -Order Number add to
-Aggregate Quality -Sand Quality -Cement Quality -Water Quality
-Aggregate Weight -Sand Weight -Cement Weight -Water measure

is added by
-Construction Ref Number load to -Order Number
-Location Construction Concrete Mixer -Construction Ref Number
-Person In charge is loaded by -Date of mixing
-No of truck
 Consist of two major activities

1. Design the technical architecture

 Technical architecture - defines the hardware,
software, and telecommunications equipment
required to run the system
2. Design system models
 This includes GUI screens that users will interface
with, database designs (see XLM/C), report formats,
software steps, etc
 Consist of two major activities

Acquire Develop all of the

hardware details of the new
and or modified
software information
system
Product Model
 Product model focus on modelling the
structure of the information describing the
products, processes, resources and other
elements of the construction process using
conceptual modelling techniques.

 This approach has been particularly

popular in product model research. It aims
at determining the data structures used for
storing construction data in databases.
 May install purchased software or may write
new custom-designed programs
 Programmers are also responsible for
documenting the program, providing an
explanation of how and why certain
procedures are coded in specific ways.
 Development phase - take all of your
detailed design documents from the design
phase and transform them into an actual
system
 Two primary development activities:
1. Build the technical architecture
2. Build the database and programs
 Both of these activities are mostly performed by IT
specialists

6-66
 verifies that the system works and meets all of the
requirements defined in the analysis phase
 Two primary testing activities:
1. Write the test conditions
 Test conditions - the detailed steps the
system must perform along with the expected
results of each step
2. Perform the testing of the system
 Unit testing – tests individual units of code
 System testing – verifies that the units of code
function correctly when integrated
 Integration testing – verifies that separate systems
work together
 User acceptance testing (UAT) – determines if the
system satisfies the requirements
Implementation and Evaluation
• The process of having systems personnel
check out and put new equipment into use,
train users, install the new application and
construct any files of data needed to use it
 Implementation phase - distribute the
system to all of the knowledge workers and
they begin using the system to perform their
everyday jobs
 Two primary implementation activities
1. Write detailed user documentation
 User documentation - highlights how to use the
system

6-72
2. Provide training for the system users
 Online training - runs over the Internet or off a CD-
ROM
 Workshop training - is held in a classroom
environment and lead by an instructor

6-73
 Choose the right implementation method
◦ Parallel implementation – use both the old and new
system simultaneously
◦ Plunge implementation – discard the old system
completely and use the new
◦ Pilot implementation – start with small groups of
people on the new system and gradually add more
users
◦ Phased implementation – implement the new
system in phases

6-74
 Maintenance phase - monitor and support
the new system to ensure it continues to
meet the business goals
 Two primary maintenance activities:
1. Build a help desk to support the system users
 Help desk - a group of people who responds to
knowledge workers’ questions
2. Provide an environment to support system
changes

6-76