INTRODUCTION TO SYSTEMS DEVELOPMENT Programmers

- Systems development could be seen as the simple - Information System professionals who modify
process of writing programs to solve the needs of existing programs or write new program to satisfy
the user. user requirements
- Unfortunately, the user knows what he wants but
Technical Specialists
has no technical expertise while the programmer
understands the computer but not the user - Those who are experts in specific technologies
environment.
- Systems analyst translates user’s needs into System Stakeholders
detailed specifications for implementation by the
- All those who are affected by the systems
programmer.
development project
Development Team - End users, managers, etc.

- Responsible for determining the specific objectives SYSTEM DEVELOPMENT LIFE CYCLE
of the system and for delivering a system that
meets these objectives - There is a well-defined process by which an
application is conceived, developed and
Typically includes: implemented.
- It gives structure to a creative process.
o Users
- In order to manage and control the development
o Managers effort, it is necessary to know what should have
o System analysts been done, what has been done, and what has yet to
o Programmers be accomplished.
o Technical specialists - The phases in SDLC provide a basis for
o Other stakeholders management and control because they define
segments of the workflow which can be identified
Project Manager
for managerial purposes and specify the documents
- Responsible for coordinating the various team or other deliverables to be produced in each phase.
members and the resources to complete a project on
time 1. Planning Stage
- Technical, business skills, people - The planning phase is the most critical step in
creating a successful system. During this phase,
Responsible for: you determine what you want to do and what tasks
to solve.
 Controlling the quality of the system being
- The planning phase involves the entire project
developed
team. The outputs from the planning stage include
 Bringing personnel on board and training them
project plans, cost estimations, and procurement
 Facilitating communications among team
requirements. When you are finished, your plan
members
should be something the entire team can
 Acquiring the various resources needed to
understand.
support the activities of the various members
of the development team
2. Analysis
System Analyst - Define and document the requirements of the end-
user of the system - what are their expectations and
- A professional with expertise in analyzing and how to fulfill them.
designing business systems - In addition, a feasibility study is made for the
- Acts as a liaison between the business side of the project, which clarifies whether the project is
house and the IT side of the house organizationally, economically, legally, and
- Collaborates with end users and IT staff to evaluate technologically feasible.
computer systems and design new ones - Systems analysis is vital in determining what a
business’ needs are, as well as how they can be
Skills and Knowledge
met, who will be responsible for individual pieces
 Solid technical knowledge of the project, and what sort of timeline should be
 Strong oral and written communication skills expected.
 Good analytical ability
 Understanding of business operations and 3. Design
processes - This phase defines the system elements,
 Good interpersonal skills components, security level, modules, architecture,
 Leadership skills various interfaces, and data types that the system
operates on.
 Computer literate
- System design defines, in general terms, how the SYSTEM PLANNING
system will look and operate. Then, an extended,
detailed design is made, taking into account all - Learn how IT Projects get started and how a
functional and technical requirements, both systems analyst evaluates a proposed project and
logically and physically. determine its feasibility.
- This stage is very important and it is necessary to - System analyst first task is: Review an IT request
allow enough time to complete this phase with the to determine if it presents a strong case or
required quality level. program code and justification.
reconfigure the systems on the servers. This will - Check company’s strategic plan and studies the
avoid wasting time in the following stages since it mission, objectives and IT needs of the
is much easier to fix errors at the design level than organization.
to redo the - Conduct a preliminary investigation if the project is
feasible (Feasibility Study)
4. Development - Submit Report to management
- This phase follows a complete understanding of the
STRATEGIC PLANNING
system requirements and specifications. This is the
process of system development when the system - process of identifying long-term organizational
design is already fully completed and goals, strategies, and resources.
understandable to all parties. - it looks beyond day-to-day activities and focuses
- In the system development lifecycle, this is where on a horizon that is 3, 5 or even 10 years in the
code is written. If the hardware part is available, future.
the system includes the hardware part, and the - Managers should be part of a strategic planning
development phase will include the configuration
and adjustment of the hardware for specific
requirements and functions.
- This part takes the most time and effort.

5. Testing and Integration

- At this stage, various components and subsystems
are assembled into one integral system. Then, the
system is tested in various modes to analyze its
state, behavior, and functioning.
- Testing can be performed by real users or by a
dedicated team of employees.
- Testing can be manual or automated to make sure
that results obtained from the system are consistent
with those intended and desired. At this stage, all
components of the information system are
integrated into a single whole.

6. Implementation
- After the testing phase, the information system
should be transferred to the production
environment for use by real users.
- This phase involves the actual installation of the
newly-developed system.
- This process involves the deployment of hardware
and software, and the corresponding settings and
configuration of all system components.
- End-users may need training to become familiar
with the system and know how to use it.

7. Maintenance
- At this final stage, the system is fine-tuned as
needed for certain improved parameters, for
example, to improve performance, increase
operational stability, reduce the risks of security
breaches or data loss.
- During this phase, periodic technical support of the
system is carried out to ensure that the system is
not out of date.
SYSTEMS PROJECT - Many organizations use a special form of systems
requests
- Systems Projects always start with a SYSTEM
- A properly designed form streamlines the request
REQUEST
process and ensures consistency
- It is the formal way of asking for IT support.
- Must be easy to understand and include clear
- Enhancement of existing system instructions
- Correction of problems - Should include enough space for all required
- Replacement of old system information and should indicate what supporting
- Or development of an entirely new information documents are needed
system
Systems Review Committees
Main Reasons for System Project
- Most large companies use a systems review
 Improved services committee to evaluate systems requests
 Better performance - Many smaller companies rely on one person to
 More information evaluate system requests instead of a committee
 Stronger controls - The goal is to evaluate the requests and set
 Reduced cost priorities
Factors That Affect Systems Projects
FEASIBILITY STUDY
Internal Factors
 Strategic plan - decisions on systems - A systems request must pass several tests, called a
projects approval will be based on the feasibility study, to see whether it is worthwhile to
company goals and objectives proceed further.
 Top managers - directives from top - It determines the probability of success of proposed
managers are a prime source of large-scale system’s development project and assesses the
system projects projects
 User requests - as users rely more heavily - Is used to aid in the decision of whether or not to
on information system to perform their proceed with the IS project.
jobs, they are likely to request even more - Helps us decide where to focus our efforts
IT services and support. - A study to ascertain the feasibility of a new system
 Information technology department - - A study to justify the NEED for a new system and
recommendations of IT staff based on clarify potential SOLUTIONS
their knowledge of business operations. - Gives management a basis for decisions
 Existing systems - errors and problems in - Identifies direction
existing systems can trigger requests for - Analysis and models help to understand system and
system projects. needs
External Factors - Focus on WHAT not HOW
 Technology - changing technology is the
major force affecting the business Four Categories
 Suppliers - sometimes company’s
1. Operational Feasibility
activities should also adjust to suppliers’
- Determines if the human resources are available to
system
operate the system once it has been installed
 Customers - systems that will also
- Users that do not want a new system may prevent it
consider the customer’s satisfactions
from becoming operationally feasible
 Competitors - upgrades of competitor‘s
products and services can also affect Vital Issues
organization’s system projects
 The economy - economic  Management support
activity/economic expansion  Users support
 Government - regulations of governments  Workforce reduction: if new system affect
workforce, what will happen to affected
PROJECT MANAGEMENT TOOLS employees
- All IT projects must be managed and controlled  Users training
- Begins with a systems request, and continues until  Users involving in new system
the project is completed or terminated

EVALUATION OF SYSTEM REQUEST 2. Technical Feasibility

- It refers to technical resources needed to develop,
Systems Requests Forms purchase, install, or operate the system
 - Users’ and analysts’ familiarity with the business
application area
- Familiarity with technology (Have we used it
before? How new is it?)
- Project size (Number of people, time, and features)
- Compatibility with existing systems

Points to be considered when assessing technical

feasibility

3. Economic Feasibility
- Means that the projected benefits of the proposed
system out-weight the estimated costs usually
considered the TOTAL COST OF OWNERSHIP
(TCO), which includes the ongoing support and
maintenance cost and the acquisition costs.
 People, IT staff and user
 Hardware and equipment
 Software
 Training cost
 Licenses and fees
 Consulting expenses
 Facility costs
 Cost of non-developing the system or
postponing the project

4. Schedule Feasibility
- Means that the project can be implemented in an
acceptable time frame.