Scribd Logo
Upload

Welcome to Scribd!

  • 112 views

    Husky Air Assignment 5 - Chapter 5 The Scope Management Plan

    Uploaded by

    SurYa PraNowo Tkj-Exorcism
    The document provides instructions for developing a scope management plan for the Husky Air project, including defining the project scope, deliverables, and scope change process. Specifically, it instructs the team to include the project name and team members, a brief description, the project's MOV, a deliverable structure chart defining project phases and deliverables, a use case diagram depicting system functionality and actors, and a defined scope change process including any related forms or logs.

    Copyright:

    © All Rights Reserved
    Download as DOC, PDF, TXT or read online from Scribd

    Husky Air Assignment 5 - Chapter 5 The Scope Management Plan

    Uploaded by

    SurYa PraNowo Tkj-Exorcism
    112 views2 pages
    The document provides instructions for developing a scope management plan for the Husky Air project, including defining the project scope, deliverables, and scope change process. Specifically, it instructs the team to include the project name and team members, a brief description, the project's MOV, a deliverable structure chart defining project phases and deliverables, a use case diagram depicting system functionality and actors, and a defined scope change process including any related forms or logs.

    Original Description:

    ada apa ajaaaa

    Original Title

    ch05

    Copyright

    © © All Rights Reserved

    Available Formats

    DOC, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    The document provides instructions for developing a scope management plan for the Husky Air project, including defining the project scope, deliverables, and scope change process. Specifically, it instructs the team to include the project name and team members, a brief description, the project's MOV, a deliverable structure chart defining project phases and deliverables, a use case diagram depicting system functionality and actors, and a defined scope change process including any related forms or logs.

    Copyright:

    © All Rights Reserved
    Download as DOC, PDF, TXT or read online from Scribd
    Download as doc, pdf, or txt
    112 views2 pages

    Husky Air Assignment 5 - Chapter 5 The Scope Management Plan

    Uploaded by

    SurYa PraNowo Tkj-Exorcism
    The document provides instructions for developing a scope management plan for the Husky Air project, including defining the project scope, deliverables, and scope change process. Specifically, it instructs the team to include the project name and team members, a brief description, the project's MOV, a deliverable structure chart defining project phases and deliverables, a use case diagram depicting system functionality and actors, and a defined scope change process including any related forms or logs.

    Copyright:

    © All Rights Reserved
    Download as DOC, PDF, TXT or read online from Scribd
    Download as doc, pdf, or txt
    of 2

    Husky Air Assignment 5 Chapter 5

    The Scope Management Plan


    Your client, Husky Air, has given your team the authority to develop the projects scope.
    The projects scope defines the project work. It includes the work boundaries and
    deliverables that you will deliver to your client.
    Please provide a professional-looking document that includes the following:
    1. Project name, project team name, and the names of the members of your
    project team.
    2. A brief project description.
    3. The projects MOV. (This should be revised or refined if necessary.)
    4. A Deliverable Structure Chart (DSC). This should be based upon the project
    life cycle and the systems development life cycle. You should begin by creating a
    hierarchical chart that defines all of the project and system development phases.
    The system development phases will depend largely on the development approach
    you will use (i.e., waterfall, rapid applications development, etc.). After you have
    identified all of the project phases, the next step in developing a DSC is to
    identify at least one project or product deliverable for each phase.
    5. A use case diagram (UCD). A UCD defines the high-level features and
    functionality that the application system should include. Although Figure 5.5
    provides an example of a use case, you can build one by:
    a. Drawing a box to represent the system boundary.
    b. Draw stick figure or people to represent the actors of the system. Actors
    can be users, managers, customers, or even other systems that will interact
    with or use the application system. Actors should be drawn on the outside
    of the system boundary. Be sure to label each actor with a descriptive
    name to describe the actors role.
    c. A use case is a particular function that application system will perform.
    Draw an oval inside the system boundary for each function, and label the
    oval with a descriptive name. Examples of use cases are update customer
    information, print employee overtime report, create new vendor record,
    and so forth. This is an important step during your project that requires a
    great deal of interaction with your client. Unfortunately, you will not have
    access to a real client so you can be creative. Keep in mind, however, that
    additional (and often unused) functionality will result require more time
    and resources to build the system. Subsequently, this will add to the
    projects schedule and budget. You and your team should keep in mind
    that any features and functionality of the system should help the
    organization achieve its MOV.
    d. Draw a connecting line to identify the actors who will make use of a
    particular use case.

    6. A Scope Change Process. Together, the DSC and UCD define what will and
    what will not be part of the project scope. In short, the project team is responsible
    for delivering everything that is listed in the DSC and UCD. Unfortunately, items
    may be overlooked and needs change. Adding deliverables or functionality to the
    system is an important decision. Therefore, develop a logical process that your
    client and team will follow for identifying, cataloging, managing, and responding
    to a scope change request. Be sure to include a templates or examples of any
    forms or logs that will be used to support the scope change process.

    You might also like