|Due By (Pacific Time)||12/17/2016 12:00 am|
Due: Thursday, December 15, 2016
You are asked to develop a software development plan (SDP) for a Law Enforcement Computer Aided Dispatch System based on the requirement specification developed by the Law Enforcement Information Technology Standards Council. You should begin by reading the executive summary, and skimming the sections detailing the business functions to be provided. Since this is a large system, you will not be required to perform a function point count of the whole system for this assignment, as you would in practice. Instead, you are asked to count function points from a representative sample, as explained below.
Note that the "use cases" in the specification each describe more than one real use case. For example, BOLO (use case 1.5) includes creating, searching, printing, and purging of BOLOs. Also note that the specification is meant to be somewhat generic and needs to be customized for each system that is built. You should document any assumptions you make about details that are not included in the specification. For example, the BOLO use case states that subject person, subject vehicle, and contact information should be recorded but doesn't specify precisely what information (subject height?, subject weight?, vehicle color?, vehicle make?, etc.) to include.
Since this is a fairly large system with significant uncertainty about the requirement details, you should plan an iterative process. Provide both a course-grained plan for the overall project, and a fine-grained plan for the first iteration of the Elaboration phase.
The coarse-grained plan should include:
1 A description of the specific 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 based on Function Point analysis and COCOMO. Provide detailed documentation of how the estimates were developed, including a table to record your function point counting data similar to the following: â€¨For each component, record a name, its type, a list of the DETs, the count of DETs, the complexity, and number of function points.â€¨â€¨For ILFs and EIFs, also record the RET count. For EIs, EOs, and EQs, also record the FTR count. If a "data function" (i.e. data store) contains more than one type of record (RET), name them and specify the DETs for each RET separately. You will probably want to refer to the lecture notes on Function Points, and the COCOMO II Calculator that we discussed in class.â€¨â€¨For the transactional functions (EIs, EOs, and EQs), you may assume that use case 1.5 (BOLO) is representative of the 28 use cases that are specified. In other words, multiply the number of function points for transactional functions from BOLO by 28. For data functions (ILFs and EIFs), you may assume that the Law Enforcement Dispatch business function (sections 1.1 - 1.10) is representative of the five business functions. In other words, multiply the number of function points for data functions from Law Enforcement Dispatch by 5.
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.
The fine-grained plan should include:
1 A detailed process diagram for the first iteration of the Elaboration phase showing all of the activities with their inputs and outputs.
2 A Gantt chart showing the task dependencies, activity schedule, and delivery dates of all artifacts.
A table showing how resources (e.g. developers) are allocated to tasks. You can refer to the members of the development team as Developer_1, Developer_2, etc. Make sure your table is consistent with the staffing profile of your course-grained plan.
out of 1971 reviews
out of 766 reviews
out of 1164 reviews
out of 721 reviews
out of 1600 reviews
out of 770 reviews
out of 766 reviews
out of 680 reviews