Uploaded by : Rohaan khan From : Gulshancampusa.wix.com

1. System—Set of components
that interact to achieve
common goal

2. Uploaded by Rohaan
From
www.gulshancampusa.wix.co
m

3.  Many failed systems were abandoned because
analysts tried to build wonderful systems
without understanding the organization.
 The primarily goal is to create value for the
organization.

4. What is a systems analyst?
Next
Responsible for designing
and developing
information system
Connection between
users and IT
professionals

5.  The project --
◦ Moves systematically through phases where each
phase has a standard set of outputs
◦ Produces project deliverables
◦ Uses deliverables in implementation
◦ Results in actual information system
◦ Uses gradual refinement

6.  Planning (Why build the system? How should
the team go about building it?)
 Analysis (Who uses system, what will it do,
where and when will the system be used?)
 Design (How will the system work?)
 Implementation (System delivery)

7. A simple process for making lunch

8.  Identifying business value
 Analyze feasibility
 Develop work plan
 Staff the project
 Control and direct project

9.  Analysis strategy
 Gathering business requirements
 Requirements definition use cases
 Process modeling
 Data modeling

10.  Design selection
 Architecture design
 Interface design
 Data storage design
 Program design

11.  Construction
◦ Program building
◦ Program and system testing
 Installation
◦ Conversion strategy
◦ Training plan
◦ Support plan

12. Process Product
Planning
Analysis
Design
Implementation
System Request
Feasibility Analysis
Workplan
System Proposal
System
Specification
New System and
Maintenance Plan

13. Waterfall model: has well-defined, linear
stages of systems development and
support. example: employee payroll
computing, online event management
system
Spiral model: shows that software is
developed using an iterative or spiral
approach rather than a linear approach.
 Example: Microsoft operating system,
Prototyping model: used for developing
prototypes to clarify user requirements.
Examples : new computer making and
military machinary

14.  Clear user requirements
 Familiarity with technology
 Complexity of system
 Reliability of system
 Time schedule
 Schedule visibility

16. Why systems fail?
 Did not support business strategies
 Poor planning and project management
 Failure to understand user requirements
 Poor cost estimating and benefit analysis
 Design defects
 Incompatible or inadequate technology
 Lack of adequate controls
 Unstructured, unmaintainable software

17. What makes successful
systems?
 User involvement
 Systems planning and project management
 Developing alternative designs
 Functional design guides detailed design
 Complete, concise, and clear documentation
 Using a coordinated, planned approach
 Post implementation reviews
 Designing for systems maintenance

18. The Project Manager is a person who has overall
responsibility for successful planning, monitoring,
control and
execution of a project. Project manager will be
accountable
for ensuring any objectives or goals that are
predetermined in
order to complete the project as and when desired by
the organization.
The Project Manager collects metrics data(such as
baseline,
actual values for costs, schedule, work in progress, and

19. 1 - 19
 Business Analyst
 Database Administrator
 Systems analyst
 Technical Lead/Architect
 Application Developers
 Software Quality Assurance Analyst
 Technical Support

20. A Business Analyst acts as a face of Customer to the
Development team, most of the time. A Business
Analyst
should be credible enough and the team should have
absolute faith in him.
Development team should be able to ask any question
regarding the system and they should believe in the
answers
that BAs provide. If they start having doubts on the
answers
BAs provide they may get tempted to develop
something that

21. A database administrator (short form DBA) is a person
responsible for the design, implementation,
maintenance and
repair of an organization's database.
The role includes the development and design of
database
strategies, monitoring and improving database
performance
and capacity, and planning for future expansion
requirements.
A database administrator (DBA) is also responsible for
the

22. A Systems Analyst is someone who works on a high level
in
an organization to make sure that all of the various
systems
and infrastructures of a non-technical nature, as well as
the
capabilities of the computer systems, are working as
well as
they can be.
A Systems Analyst examines distribution of work on a
project, how it is originated, how it is created, and how
it is
disseminated, and will be working closely with end users

23. The major role of an Application Developer is to consult
with
the departmental heads, in order to make sure that the
product
developed meets the customer’s requirement.
The main responsibilities of the Application Developer
are to:
 identify, define, and model the application
requirements.
 define data structures and distribution to satisfy the
application solution.
 prepare deliverables to support the development and
deployment of the solution such as application guides

24. The Quality Assurance Analyst's role is to develop and
establish quality assurance standards and measures for
the
information technology services within the organization.
This
individual will also gather and analyze data in support of
business cases, proposed projects, & systems
requirements.
This will include writing test plans and scripts for
tracking
defects and fixes in product development, software
application
development, information systems, and operations

25.  The Systems Development Lifecycle consists of
four stages: Planning, Analysis, Design, and
Implementation
 There are six major development methodologies:
the waterfall method, the parallel development
method, the phased development method, system
prototyping, design prototyping, and agile
development.
 There are five major team roles: business analyst,
systems analyst, infrastructure analyst, change
management analyst and project manager.