Software Measurement, Goal–Question–Metric Analysis and Process Model Evaluation for DETO
This Measures and Models in Software Engineering coursework uses the Doolan Executive Taxi Service Online (DETO) case study to assess the application of software measurement techniques, Goal–Question–Metric analysis and software process modelling. The assignment requires students to connect quantitative software-engineering measures with practical organisational objectives and to critically evaluate suitable development-process approaches for a safety- and reliability-sensitive software system. 7COM1024_MMSE_ Def_CW_Brief 202… Task 1 focuses on software measurement using Unadjusted Function Points. Students analyse part of the DETO web-based email attachment system and identify relevant functional elements, including user inputs, reports to users, prompts and responses, interfaces to external systems or files, and internal logical files. Appropriate weights must then be selected to calculate the unadjusted functional-point value. 7COM1024_MMSE_ Def_CW_Brief 202… Task 2 requires application of the Goal–Question–Metric (GQM) approach to evaluate the effectiveness of the DETO website. Students identify the object under measurement and define the purpose, quality focus, viewpoint and context. They then develop two measurable organisational goals, formulate relevant questions for each goal and identify metrics that could be collected to evaluate website performance and support the company's priority of attracting new customers. 7COM1024_MMSE_ Def_CW_Brief 202… Task 3 moves from software measurement to software process models. DETO is considering a sophisticated on-board navigation system for its next generation of vehicles, where fast development, high quality, reliability and integration with the existing website are strategically important. Students select two software process models and critically evaluate their suitability for the project. The discussion should compare their distinguishing characteristics against alternative approaches, identify development challenges, evaluate project risks and pitfalls, and propose appropriate risk-mitigation strategies. 7COM1024_MMSE_ Def_CW_Brief 202… The main discussion for Task 3 is limited to 2,000 words ±10% and must use the Harvard referencing system, with at least 10 sources expected. The brief specifically requires original prose and prohibits bullet points, lecture materials and diagrams for this section. 7COM1024_MMSE_ Def_CW_Brief 202… Overall, the assessment integrates functional software measurement, GQM-based metrics, process-model evaluation, software quality, reliability, systems integration and project risk management within a realistic software-engineering business scenario.
Read Model Answer →