The Scope Management Plan Knights Air Service
Your client, Knights Air Service, has given your team the authority to develop the project’s scope. The project’s 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:​​​​​​​
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.
A use case diagram (UCD). Use Case Diagrams belong to the behavioral category of the Unified Modeling Language. Find out more information at uml. org (Links to an external site.)Links to an external site. A UCD defines the high-level features and functionality that the application system should include. Here are some brief steps to building a UCD:
Draw a box to represent the system boundary.
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 actor’s role.
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 project’s 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.
Draw a connecting line to identify the actors who will make use of a particular use case.
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 need changes. 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 templates or examples of any forms or logs that will be used to support the scope change process.