Benghazi University

Faculty of Information Technology

Information Systems Development

Course Code: IS362

Prepared By: lutfi Ali Abukhzam

Helped by: Wesam Ben Amer

2017-2018
 AN OVERVIEW OF SYSTEMS DEVELOPMENT

• The introduction of a new information system involves much

more than new hardware and software.
• It also includes changes in jobs, skills, management, and
organization.
• When we design a new information system, we are
redesigning the organization.
• System builders must understand how a system will affect
specific business processes and the organization as a whole.

2
 cont…
• The activities that go into producing an information system
solution to an organizational problem or opportunity are called
systems development
• The systems development activities usually take place in
sequential order.
• But some of the activities may need to be repeated or
employed

3
 System Development

System development is a set of activities

used to build an information system
An information
system (IS) is a System development
A system is a set of collection of activities are grouped
components that hardware, software, into phases,
interact to achieve a data, people, and collectively called the
common goal procedures that work system development
together to produce life cycle (SDLC)
quality information

4
 System Development Cycle
• What are the phases of the system development cycle?
Phase 2. Analysis
 Conduct preliminary investigation
Phase 1. Planning  Perform detailed analysis activities:
 Review project requests
Phase 3. Design
Study current system  Acquire hardware
 Prioritize project Determine user requirements and software, if
requests necessary
Recommend solution
 Allocate resources  Develop details of
 Identify project system
development team

Phase 5. Support Phase 4. Implementation

 Conduct post-implementation  Develop programs, if necessary
system review  Install and test new system
 Identify errors and enhancements  Train users
 Monitor system performance  Convert to new system

5
 Every Software Development Life Cycle
(SDLC) Model

• There are six phases in :

1. Requirement gathering and analysis
2. Design
3. Implementation or coding
4. Testing
5. Deployment
6. Maintenance

6
 System Development

• System development should follow three general

guidelines:

Group activities or tasks into phases

Involve users

Define standards

7
 System Development Cycle
• systems analyst

Responsible for designing and

developing information system

Liaison between users and IT

professionals

8
 System Development Cycle
• Project team

Formed to work on project from beginning to end

Consists of users, systems analyst, and other IT professionals

Project leader—one member of the team who

manages and controls project budget and
schedule

9
 System Development Cycle
• Project Management
• Project management is the process of planning, scheduling, and
then controlling the activities during system development
• To plan and schedule a project efficiently, the project leader
identifies:

Required Time estimates

Project scope
activities for each activity

Activities that
Cost estimates Order of
can take place
for each activity activities
at the same time

10
 System Development
Software Quality Characteristics:
 Maintainability is "the ease with which changes can be made to satisfy new
requirements or to correct deficiencies“
 Reusability is "the ease with software can be reused in developing other
software“.
 Reliability is "the frequency and criticality of software failure, where failure is
an unacceptable effect or behavior occurring under permissible operating
conditions"
 Portability is "the ease with software can be used on computer configurations
other than its current one“.
 Efficiency is "the degree with which software fulfills its purpose without waste
of resources"

11
 System Development
• What is Feasibility
• Feasibility is a measure of how suitable the development of a
system will be to the organization

Operational Schedule Technical Economic

feasibility feasibility feasibility feasibility

12
 Feasibility study
The systems analysis also includes a feasibility study to determine
whether that solution is feasible, or achievable from a financial,
technical, and organizational standpoint.

• Economic feasibility
– The determination of whether the project makes financial sense
and whether predicted benefits offset(‫ (الفوائد المتوقعة‬the cost and
time needed to obtain them

13
 Cont…

• Legal feasibility or regulations

– may prevent or limit a systems development project.
• Operational feasibility
– The measure of whether the project can be put into action
or operation.
• Schedule feasibility
– The determination of whether the project can be completed
in a reasonable amount of time.

14
 System Development
What is the Documentation ?

• Documentation is the collection and summarization of data and

information
– A project notebook contains all documentation for a single project
• Users and IT professionals refer to existing documentation when
working with and modifying current systems

15
 System Development
What is the Documentation ?
• A requirement is something that the product must do or
quality that the product must have. A requirement exists
either because the type of product demands certain functions
or qualities, or the client wants that requirement to be a part
of the delivered product. (Robertson & Robertson 1999)
• In practice requirements are: A mixture of problem
information, statements of system behaviour and properties
and design and manufacturing constraints (Kotonya &
Sommerville, 2002)

16
 System Development
Different level of requirements
• Business requirements: (why the organization is undertaking the
project)
• User Requirements: what the user does with the system, what
activities users must be able to perform
• System Requirements: Set out the system services in detail
• Software Design Specifications (SDS): Functional/ Non-
functional requirements

17
 System Development
Software design specification requirement

Functional requirements
• Statements of services the system should provide, how system
should react to inputs and how the system should behave
• Also these may explicitly state what the system should not do
Non-functional requirements
• Constrains on the services or function offered by the system.
These include timing constrains, contrains on développement
processor, standards etc.

18
 System Development

Characteristics for successful requirement determination

• Impersonality: question everything

• Impartiality: business problem vs. solution
• Relaxing constraints: ‘Anything is possible’
• Attention to details: ‘Every fact must fit with every other fact’.
• Reframing: Need to challenge to look at the organization in new
ways

19
 System Development

Requirement ( change / variations)

• At requirement stage – change to document and/or diagram.
• At design stage – require re-checking of assumptions and
implications.
• At programming stage – may have to revisit and re-write code.
• At testing stage – re-visit analysis and/or design and/or code.
• After production and release all of the above may have to be re-
performed plus data may have to be re-stored.

20