Scribd
Upload
38 views

IT-510 Module 2 Part Two

A systems analyst must develop a work breakdown structure (WBS) that organizes tasks in a logical order with dependencies defined. As tasks are completed, the systems analyst continually adjusts future tasks and the project schedule while ensuring milestones are met on time. Object oriented modeling identifies system objects and their attributes/behaviors and allows the systems analyst to build independent pieces before integrating into a full system design.

Uploaded by

petetg5172
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
38 views

IT-510 Module 2 Part Two

A systems analyst must develop a work breakdown structure (WBS) that organizes tasks in a logical order with dependencies defined. As tasks are completed, the systems analyst continually adjusts future tasks and the project schedule while ensuring milestones are met on time. Object oriented modeling identifies system objects and their attributes/behaviors and allows the systems analyst to build independent pieces before integrating into a full system design.

Uploaded by

petetg5172
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

Project Scheduling and Control

Scheduling a project requires a variety of methods and


techniques. A project manager must be highly skilled in the
area of scheduling. For systems analysts, the need to
schedule and control aspects of their work does not
require the same level of knowledge as project managers.
However the same methods and techniques apply.

A systems analyst will first need to develop a work


breakdown structure (WBS). This is a high level
organization of the work to be completed. Tasks are then
added to the WBS. Tasks are the actions to perform and
are verbs. Once you have the WBS and its tasks defined,
you then begin to connect them in a logical order. Some
tasks require that a predecessor task completes before
they can start. When we define tasks according to these
project management rules, as the project progresses and
is being tracked, the successor tasks will continue to
reschedule as the predecessor tasks complete.

As the systems analyst tracks the completed tasks and


manages the current tasks, the analyst continually adjusts
the future tasks of the project plan as well. For example, if
the plan was scheduled to complete data design in ten
days and the design was completed in five days, the plan
gained five days. However, gaining five days does not
mean the project will end five days earlier. The schedule is
a very complex network of tasks, so being able to read a
project schedule in Microsoft Project will help the systems
analyst control the project. When controlling a project, the
systems analyst needs to focus on completing each
planned task, while adding tasks that were not initially
planned, and still make the target delivery dates. The
target deliveries are typically defined as milestones. The
milestone dates will be the dates that something must be
delivered. In a typical project plan, a milestone may be
three months from the starting point. The systems analyst
should expect that there will be scope increases and
decreases based on the execution of work tasks.
However, the milestone is an anchor target date that the
team should try not to move. Project management and
control is the execution portion of project management
methods and techniques that are needed to make the
milestone date.

For the purpose of the course, it is important to


understand the concepts of project management and the
systems analyst role. Note that the fundamentals
explained in the course are an introduction to project
management concepts. Through further studies, which are
structured specifically on project management, students
will learn the application of project management
techniques and methods. In Module Three, students will
begin to design the system using object oriented
modeling. Object oriented modeling is an approach that
identifies system objects, classifies system objects,
defines system objects, and describes the attributes and
behaviors of system objects. Using object oriented design,
the systems analyst can build out small pieces of the
system independently of each other before integrating into
a full system design and architecture.

You might also like