Download as pptx, pdf, or txt
Download as pptx, pdf, or txt
You are on page 1of 34

CSC316: Systems

Analysis and Design

1
Course Schedule
 Lecture Schedule:
 Tuesdays 1:00pm - 3:00pm

 Class Venue: E303

 Please attend your lectures. Attendance is mandatory

2
Learning Outcomes
Learning Outcomes
At the end of this course, students should be able to:
1. describe system requirements gathering techniques;
2. explain data modelling technique (entity relationship
modelling);
3. explain process modelling technique (data flow diagram);
4. describe system architectural design;
5. describe process and database design; and
6. explain user interface design.

3
Outlines
This course provides a hands-on introduction to a number of Systems Analysis
and Design activities and concepts. It will include the following topics:
Week 1: Introduction to Systems Analysis and Design
Week 2: Systems Design Life Cycles (SDLC)
Week 3: Project Management
Week 4: Requirements Gathering
Week 5: Use Cases and Activity Diagrams
Week 6: Domain Modeling
Week 7: Data Modeling
Week 8: Data and Dataflow Modeling
Week 9: Database design and OO Design
Week 10: Architectural Design
Week 11: Deployment and Testing 4

Week 12, 13: Project time


Course Material 1
 Textbooks and References
 Recommended Text:
Systems Analysis & Design (5th Edition).
Alan Dennis, Barbara Haley Wixom and
Roberta M. Roth
 References
This course will make use of a number of
resources, including:
 book chapters
 online articles
 Use lecture notes/slides as study
guide
5
Course Material 2
 Textbooks and References
 Recommended Text:
Systems Analysis And Design in a
Changing World (6th Edition).
John W. Satzinger, Robert B. Jackson
and Stephen D. Burd
References
This course will make use of a number of
resources, including:
 book chapters
 online articles
 Use lecture notes/slides as study
6
guide
PROJECT
MANAGEMENT
The Project
 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
Project Management
 Management: is getting things done through other people.
 Project: a planned undertaking that has a beginning and
an end that produces a predetermined result or product.
 Project management is a special type of management.
 Project Management: is organizing and directing other
people to achieve a planned result within a predetermined
schedule and budget.
Five Functions of
Management
Planning

Directing Staffing

Controlling
Organizing
10
PM Tasks: Analysis Phase
 Monitor and control scope.
 Monitor and control progress.
 Update schedule.
 Conduct status reviews.
 Organize teams.
 Provide leadership for teams.
 Coordinate with users/clients.
 Evaluate risks.
 Plan in detail design phase.
 Make presentation.
PM Tasks: Design Phase
 Monitor and control scope.
 Monitor and control progress.
 Monitor and control budget.
 Conduct status reviews.
 Coordinate team member training.
 Track open issues.
 Encourage/lead team members.
 Monitor technical problems.
 Reorganize team assignments.
 Monitor subcontractor/vendors.
 Plan in detail implementation phase.
PM Tasks: Analysis Phase
 Monitor and control scope.
 Monitor and control progress.
 Monitor and control budget.
 Conduct status reviews.
 Reorganize team assignments.
 Coordinate with users/clients.
 Track testing and quality.
 Take corrective action.
 Coordinate data conversion.
 Conduct system installation.
 Conduct post-implementation review.
Project Management Tasks
 Project Scope Management: defining and controlling the functions

that are to be included in the system as well as the scope of the work

to be done by the project team.

 Project Time Management: building a detailed schedule of all project

tasks and then monitoring the progress of the project against

defined milestones.

 Project Cost Management: calculating the initial cost/benefit

analysis and later updates and monitoring expenditures as the project

progresses.
Project Management Tasks
 Project Quality Management: establishing a total plan for ensuring

quality, which includes quality control activities for every phase of

the project.

 Project Human Resource Management: recruiting and hiring project

team members; also training, motivating, team building and

implementing related activities to ensure a happy productive team.

 Project Communications Management: identifying all stakeholders

and key communications to each; also establishing all communications

mechanisms and schedules.


Project Management Tasks
 Project Risk Management: identifying and reviewing throughout the

project all potential risks for failure and developing plans to reduce

these risks.

 Project Procurement Management: developing requests for proposals,

evaluating bids, writing contracts and then monitoring vendor

performance.
Project Initiation
 Projects are initiated for various reasons:

 To respond to an opportunity.

 To resolve a problem.

 To conform to a directive.
The Project Planning Phase
 The planning phase consists of the activities that are required

to get the project organized and started:

 Define the project.

 Produce the project schedule.

 Confirm project feasibility.

 Staff the project.

 Launch the project.


Defining the Problem
 Carefully defining the problem is one of the most important

activities of the project.

 This activity defines the target that you want to hit.

 If the target is ill defined, then all subsequent activities will

lack focus.

 One primary cause of project failure is an unclear objective.


Defining the Problem
 The first task in this activity is to review the business needs

that originally initiated the project.

 Business Benefits: the benefits that accrue to the

organization; often measured in monetary terms.

 Business benefits are normally described in terms of the

influences that can change the financial statements,

either by decreasing costs or by increasing revenues.


Defining the Problem
 The second task in this activity is to identify, at a high level,

the expected capabilities of the new system.

 System Scope Document: a document –containing description,

business benefits, and system capabilities – to help define the

scope of a new system.

 Proof of Concept Prototype: a very preliminary prototype built

to illustrate that a solution to a business need is feasible.

 Context Diagram: a graphical diagram showing the scope of the

system.
Producing the Project Schedule
 Phase: is made up of a group of related activities.
 Activity: is made up of a group of related tasks.
 Task: is the smallest piece of work that is identified and scheduled.
 It may not be possible to schedule every task in the entire
project.
 It is too early to know all the tasks that will be necessary.
 However, one of the requirements of the project planning phase
is to provide estimates of the time to complete the project and
the total cost of the project.
 The payment of salaries to the project team is one of the major
factors of the project cost.
Confirming Project
Feasibility
 Economic feasibility.

 Organizational and cultural feasibility.

 Technological feasibility.

 Schedule feasibility.

 Resource feasibility.
Economic Feasibility
 Economic feasibility:
 Is the anticipated value of the benefits greater
than projected costs of development?
 Does the organization have adequate cash flow to
fund the project during the development period?
Staffing the Project
 Project manager should:
 Develop a resource plan for the project.
 Identify and request specific technical staff.
 Identify and request specific user staff.
 Organize the project team into workgroups.
 Conduct preliminary training and team-building
exercises.
Critical Areas
 Communications

 Databases

 Programming

 Hardware

 Industry Standards

26
Management Hierarchy
 Strategic
Systems
 Middle
Needs
 Operational

27
Project Management

Analysis
and • Resources
Design • Time
Activities

28
Project Fundamentals

 Project Initiation
 Determining Feasibility
 Scheduling
 Managing Activities and
Personnel

29
Project Team Skills
 Project team members are change agents who find ways
to improve their organization
 A broad range of skills is required, including
 Technical
 Business
 Analytical
 Interpersonal
 Management
 ethical
Project Team Roles
Role Responsibilities
Business Analyst Analyzing the key business aspects of the system
Identifying how the system will provide business value
Designing the new business processes and policies
Systems Analyst Identifying how technology can improve business
processes
Designing the new business processes
Designing the information system
Ensuring the system conforms to IS standards
Infrastructure Ensuring the system conforms to infrastructure
Analyst standards
Identifying infrastructure changes required by the
system
Change Developing and executing a change management plan
Management Developing and executing a user training plan
Analyst
Project Manager Managing the team
Developing and monitoring the project plan
Assigning resources
Serving as the primary point of contact for the project
Project Team Roles
 Business analyst (business value)
 Systems analyst (IS issues)
 Infrastructure analyst (technical issues – how the system will
interact with the organization’s hardware, software,
networks, databases)
 Change management analyst (people and management issues)
 Project manager (budget, time, planning, managing)

Slide 32
Summary
 The Systems Development Life Cycle (SDLC) consists of
four stages: Planning, Analysis, Design, and
Implementation
 The Major Development Methodologies:
 Structured Design
 Waterfall Method
 Parallel Development
 Rapid Application Development (RAD)
 Phased Development
 Prototyping (system prototyping)
 Throwaway Prototyping (design prototyping)
 Agile development
 eXtreme Programming
 Project Team Roles
Summary
 There are five major team  Project team members are
roles: change agents who find ways
 business analyst to improve their organization
 systems analyst  A broad range of skills is
 infrastructure analyst required, including
 change management  Technical
analyst  Business
 project manager.  Analytical
 Interpersonal
 Management
 ethical

You might also like