Project Phase 1

M&IS 44048 Software Integration

Content: Feasibility Study, Analysis, Schedule

Description: In this phase you lay the foundation for your project. Your activities and deliverables for this phase are divided into three sections:
  1. Feasibility Study

    Decide if what the client wants is realistic or a "pipe dream." Answer these questions (and others too that you invent): can technology be used to do what the client wants? is there sufficient time this semester? does your team have the right personnel? is your client accessible?

  2. Analysis

    User Requirements

    Here you develop a strong sense of what the client really wants. Document your understanding of the client's needs in such a way that they can be easily and correctly interpreted by the client. The objective is to ensure that you are going off in a direction that will satisfy the client when you are finished. This activity requires a sign-off by the client indicating approval before you are permitted to go to Phase 2. This means that you have to move fast and get the approval before Phase 1 is due. This is not a detailed design of how the finished application will be built or operate, but this is a complete presentation of features that the system will deliver. Use charts, pictures and text to portray your analysis. Prepare a form for the client's signature indicating approval - include this form with your Phase 1 submission.

    Back up your recommendations by interviewing stakeholders and summarizing their interests. Ask your instructor for help here. What/who are stakeholders? How many? What do we ask? What does it mean?

    Technologocal Potential

    What technology platform(s) are you planning to use. Will the candidate technologies meet the client requirements? Will it run on the server? What lead time is needed for installation and training? Are there alternative platforms? What are they? Rank them somehow (you decide). How did you make your selections? Do you have enough resources? If not what are you going to do about it?

  3. Schedule

    Prepare the road map for the rest of the project. Decide what must be done and who is to do it. Determine the correct sequencing of activities so that no single activity can hold up the whole project. You don't decide on the technical platform here - but do decide how the evaluation will be made. Allocate responsibilities - this can change as needed as the project becomes more clear - but make initial assignments with due dates. Decide who is going to lead the discussion with the client - not everyone even needs to meet the client at all or for all meetings. Decide who is the team "coordinator" - the person responsible for maintaining the schedule. In essence, plan out all that you possibly can now about the project. Use tables and charts to display the information.

    Prepare the road map for the rest of the project.

  4. Phase Report Table of Contents

    1. Executive Summary

    2. Brief Description of Client Need/Desire

    3. Feasibility Study

    4. Analysis Report

    5. Yes/No and Justification

    6. Schedule & Responsibilities - think about how to capture and present this data. It is for your use in controlling the project. How can you monitor your schedule to ensure your success?

    7. Resource Allocation (show that your team resources are balanced)