I\'m not so sure where to start. we need a course grained plan that includes: \"

Question

I'm not so sure where to start. we need a course grained plan that includes: "1. A description of process to be used, including the artifacts to be developed and the level of ceremony to be used. Provide a rationale to justify these decisions. 2. Estimates of the overall cost and effort required to build the system. Include detailed documentation of how the estimates were developed. You may assume that use cases 1.5, 1.7, and 1.8 are a representative sample of the 28 use cases that are specified. 3. Documentation of any assumptions that were made in estimating cost and effort. 4. A schedule showing the major milestones and the dates when they will be delivered. 5. The staffing profile for the project (i.e. number of developers required during various stages of development). 6. A risk analysis outlining the major risks and strategies for mitigating the risks. You may base your risk analysis on the executive summary and the use cases that you used for cost and effort estimates." as well as a Fine-Grained plan that includes: "1. A detailed process diagram for the first iteration or phase of the project showing all of the activities with their inputs and outputs. 2. A Gantt chart showing the activity schedule, resource allocation, and delivery dates of all artifacts."

Explanation / Answer

Software Development Principles Software Development Phases 1. Inception Phase 2. Elaboration Phase 3. Construction Phase 4. Transition Phase Project Management Customer Portal Software Development Principles These principles are based on the Rational Unified Process (RUP) methodology, and include: Iterative Software Development On larger projects, each iteration lasts for an agreed time period, at which point the latest version of the software is tested, demonstrated and reviewed, allowing us to achieve: Concrete evidence of progress for the customer An opportunity for feedback and continuous improvement Agreement on the overall framework and project direction Risk Management We organise our work in such a way as to deal with the biggest risks first. This may involve investigating any unknown technologies which will be used on the project, or specifying and implementing the most important scenarios in the project. Correct Architecture Design It is essential to focus on the correct software architecture, which has a major bearing on factors such as scalability, performance and maintainability. Once the architecture is in place, it acts as the solid foundation upon which the rest of the application can be safely built. Software Development Phases CAD Schroer's software development projects are typically split into four main phases, which end when key objectives have been met: 1. Inception Phase Initial phase for building understanding of type and scope of system; producing cost estimates This phase deals with project requirements, initial concepts and scope. It sets out clearly what the project is trying to achieve. It usually includes a period of requirement gathering and analysis (which has strong commercial and marketing implications). The deliverables of the inception phase would normally be: A business case for the project/product An outline requirements specification for the product An initial design specification for the product (high level) An initial project plan An initial project risk assessment Budgetary estimates for the subsequent project phases Some of these deliverables would be produced by the customer (e.g. business case & requirements specification). Other deliverables would be produced by CAD Schroer (e.g. functional specifications, initial design specification, initial project plan, initial risk assessment & budgetary estimates). Some projects only include an inception phase, after which the customer would decide whether to perform additional Inception Phase work to build confidence or proceed to the Elaboration Phase. 2. Elaboration Phase Prototyping phase in which technical tasks are delineated and perceived risks are quantified and dealt with The overall purpose of the Elaboration phase is to flesh out the project by further assessing feasibility, refining the initial design, mitigating foreseeable risks, and quantifying the anticipated work required, before expending budget on any large scale or non-critical development work. Specific objectives and deliverables of the Elaboration Phase are to: Investigate how best to satisfy the project requirements Identify any suitable cost and time saving third party components, tools & libraries Identify, analyse and find solutions for any major areas of foreseeable risk Develop a design for the product's architecture Develop a design for the product's user interface (main layout and forms) Develop a proof of concept deliverable to: - Demonstrate the design and how it satisfies the main product use cases - Prove the suitability of any chosen third party components, tools & libraries - Prove solutions to deal with foreseeable areas of major risk - Assess design performance and ease of learning & speed of use - Provide an opportunity for feedback on the design - Generate confidence in the design The work performed in the Elaboration phase facilitates the refinement of the original proposals and budgetary estimates by CAD Schroer for subsequent phases to a much higher degree of accuracy, prior to commencement of the subsequent phases. 3. Construction Phase Implementation phase where the remainder of functionality is implemented, and other project deliverables are concluded The purpose of the Construction phase is to carry out the remaining project development work (usually the bulk of the development work) using the results of the Elaboration phase as the basis for this. It is normal for this phase to contain one or more sub-phases or "iterations" (in RUP terminology), especially for large projects. Each iteration provides an opportunity to deliver an increasingly complete solution that can be tested by the customer. The deliverables of each iteration also offer an opportunity to provide feedback that can be incorporated into subsequent iterations. Depending on the project size and duration, each iteration would typically be planned to last for 4 weeks. The work content of each iteration is usually largely made up of structured work content formulated at the end of the Elaboration phase. However, as feedback can also be incorporated to refine earlier work and incorporate new important ideas, or responses to emerging business opportunities, there is often a degree of organic development as well. This iterative approach usually gives a good balance of planned, well structured development, and a prudent opportunity to refine previous work and adapt the overall development plan to suit the customer's changing requirements, which inevitably arise on a large project, as do new ideas with the benefit of hindsight. In short, it maximises the likelihood of delivering what the customer ultimately really wants, as opposed to what was initially conceived. 4. Transition Phase Handover phase The purpose of the Transition phase is to hand over project collateral to the customer and deliver any other services required in conjunction with project completion. Typical items we deliver include: Source code Key knowledge Documentation Implementation In-situ Testing On-site Training Any other materials developed during the project Depending on the nature of the project, we often work alongside the customer's team for a specified period of time to ensure a smooth handover. Project Management CAD services encompass the full product life cycle. Although our customers often appoint their own project managers to oversee their interests in the projects we undertake, our own experienced project managers ensure that we meet customer requirements on project planning, progress meetings and weekly status reports. Where customers stipulate no project management requirements, CAD deploys its own in-house procedures to ensure that projects are run consistently and professionally.

Related Questions

Navigate

• Browse (All)
• Browse I
• Subjects

---

---

Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.