Minggu 5 - Software En Gene Ring

8/3/2019 Minggu 5 - Software En Gene Ring

1/28

PROJECT SCHEDULING AND TRACKING

Week 5 Software Engenering

1


2/28


2

What is it? Youve selected an appropriate processmodel, youve identified the software engineering tasks

that have to be performed, you estimated the amount of

work and the number of people, you know the deadline,

youve even considered the risks. Who does it? At the project level, software project

managers using information solicited from software

engineers. At an individual level, software engineers

themselves.


3/28


(Cont..)

3

Why is it important? In order to build a complexsystem. There are very difficult to understand without aschedule. its also virtually impossible to assess progresson a moderate or large software project without adetailed schedule.

What are the steps?

1. Tasks dictated by the software process model arerefined (disesuaikan) for the functionality to be built.

2. Effort and duration are allocated to each task.

3. Task network (also called an activity network) iscreated in a manner that enables the software team tomeet the delivery deadline established.


4/28


(Cont..)

4

What is the work product? The project schedule andrelated information are produced.


5/28

5

Software project schedulingis an activity that distributes

estimated effort across theplanned project duration by

allocating the effort tospecific softwareengineering tasks.


6/28

7.1 BASIC CONCEPTS

6

Many reasons why software is delivered late:

1. An unrealistic deadline established.

2. Changing customer requirements that are not reflected inschedule changes.

3. underestimate of the amount of effort and/or the number of

resources that will be required to do the job4. Predictable and/or unpredictable risks that were not

considered when the project commenced.

5. Technical difficulties that could not have been foreseen inadvance.

6. Human difficulties that could not have been foreseen inadvance.

7. Miscommunication among project staff that results in delays.

8. A failure by project management to recognize that theproject is falling behind schedule and a lack of action to

correct the problem


7/28

Basic Principles

7

Compartmentalization. The project must becompartmentalized into a number of manageable

activities and tasks.

Interdependency. The interdependency of each

compartmentalized activity or task must be determined. Time allocation. Each task to be scheduled must be

allocated some number of work units (e.g., person-days of

effort).

Effort validation. project manager must ensure that nomore than the allocated number of people have been

scheduled at any given time.


8/28

Basic Principles (Cont..)

8

Defined responsibilities. Every task that is scheduledshould be assigned to a specific team member.

Defined outcomes. Every task that is scheduled should

have a defined outcome (work product).

Defined milestones. Every task or group of tasksshould be associated with a project milestone. A

milestone is accomplished when one or more work

products has been reviewed for quality and has been

approved.


9/28

7.2 THE RELATIONSHIP BETWEEN

PEOPLE AND EFFORT

9

As the size of a project increases, more people mustbecome involved.

Unfortunately, adding people late in a project often has a

disruptive effect on the project, causing schedules to slip

even further. Because they must learn the system, and the people who

teach them are the same people who were doing the

work.

more people increase the number of communicationpaths and the complexity of communication throughout a

project.


10/28

7.3 DEFINING A TASK SET FOR THE

SOFTWARE PROJECT

10

A number of different process models were described inChapter 2, no single set of tasks is appropriate for all

projects.

A task set is a collection of software engineering work

tasks, milestones, and deliverables that must beaccomplished to complete a particular project.

An effective software process should define a collection

of task sets, each designed to meet the needs of different

types of projects.


11/28

7.3 DEFINING A TASK SET FOR THE

SOFTWARE PROJECT (Cont..)

11

Task sets are designed to accommodate different types ofprojects and different degrees of rigor. Beberapa jenis

project antara lain:


12/28

7.3.1 Degree of Rigor

12

Casual. Semua proses aktivitas kerangka kerja (Bab 2)diterapkan, tetapi hanya tugas minimum yang ditetapkandiperlukan.

Structured. Sebagian besar kegiatan dan tugas-tugas dalamframewark yang masih terkait sesuai dengan jenis proyek akan

diterapkan. SQA, SCM, dokumentasi, dan tugas-tugaspengukuran akan dilakukan cara yang efisien.

Restric (ketat). Proses dari framework secara lengkap akanditerapkan dengan tingkat disiplin yang akan menjamin kualitastinggi.

Quick reaction (reaksi cepat). Kerangka proses akanditerapkan, tetapi hanya pada situasi darurat saja, dengan caramenerapkan tugas-tugas penting untuk mempertahankanberkualitas yang baik.


13/28

7.3.1 Degree of Rigor (Cont..)

13

The project manager must develop a systematic approachfor selecting the degree of rigor that is appropriate for a

particular project.

To accomplish this, project adaptation criteria are defined

and a task set selector value is computed.


14/28

7.3.2 Defining Adaptation Criteria

14

Kriteria adaptasi digunakan untuk menentukan tingkatkekakuan yang direkomendasikan dimana proses

perangkat lunak harus diterapkan pada sebuah proyek


15/28

7.3.2 Defining Adaptation Criteria (Cont..)

15

Each of the adaptation criteria is assigned a grade thatranges between 1 and 5

1 represents a project in which a small subset of process

tasks are required and overall methodological and

documentation requirements are minimal 5 represents a project in which a complete set of process

tasks should be applied and overall methodological and

documentation requirements are substantial


16/28

COMPUTING THE TASK SET SELECTOR

16


17/28

COMPUTING THE TASK SET SELECTOR

AN EXAMPLE

17


18/28

7.3.4 Interpreting the TSS Value and

Selecting the Task Set

18


19/28

7.4 SELECTING SOFTWARE ENGINEERING

TASKS

19

Concept development projects are approached byapplying the following major tasks:


20/28

7.4 SELECTING SOFTWARE ENGINEERING

TASKS (Cont..)

20


21/28

7.5 REFINEMENT OF MAJOR TASKS

21

Contoh pendefinisian tugas-tugas dalam Concept

scoping ada di ebook halaman 179 s.d 180


22/28

7.6 DEFINING A TASK NETWORK

22


23/28

7.7 SCHEDULING

23


24/28

7.7 SCHEDULING (Cont..)

24


25/28

7.7.2 Tracking the Schedule

25

Project schedule defines the tasks and milestones that mustbe tracked and controlled as the project proceeds.

Tracking can be accomplished in a number of different ways:


26/28

7.9 ERROR TRACKING

26

Project team creates work products (e.g., requirementsspecifications or prototype, design documents, source

code). But the team also creates errors associated with

each work product.

Error tracking allows you to compare current work withpast efforts and provides a quantitative indication of the

quality of the work being conducted.

Any errors that are not uncovered (but found in later

tasks) are considered to be defects,D.


27/28

SUMMARY

27

Scheduling (penjadwalan) adalah puncak dari kegiatanperencanaan yang merupakan komponen utama

manajemen proyek software.

The characteristics of the project are used to adapt an

appropriate task set for the work to be done. JaringanTugas (task network) menggambarkan tugas

masing-masing engineering, dengan memperhatikan

ketergantungan pada tugas-tugas lain, dan diproyeksikan

dalam durasi. Using the schedule as a guide, the project manager can

track and control each step in the software process.


28/28

Selesai

28

Next . SOFTWARE QUALITY ASSURANCE

Date post:	07-Apr-2018
Category:	Documents
Upload:	fredymbee2934
View:	221 times
Download:	0 times

Minggu 5 - Software En Gene Ring

Documents