Recent Question/Assignment

Assessment 1 – Case Study & Questioning
Instructions:
This is an individual assessment.
In this assessment you will be working through a number of written tasks based on case scenarios and research that relate directly to competency for this cluster.
Duration:
Trainer will set the duration of the assessment.
Software Development Methodologies – Assessment Task 1 LAST UPDATED: March 2018, Version No. 1.0

Your tasks:
Task 1 — Identify stakeholders
Read the scenario below:
Southern Dental Services is a small dental practice in a regional town. There are two dentists: Pamela Jones and Brian Huang. The practice has four support staff to manage the day-to-day running of the practice: Jane Emerson, who looks after the appointments; Brenda Gale, who handles the accounts; Keith Dickson, who manages the patient details; and Pauline Santoro, who organises the ordering of supplies, etc. Pauline obtains most of the supplies for the clinic from David Andrews, who runs a business selling medical and dental supplies. She orders all the other office-related products from Peter Smith’s business, OfficeStuff. The clinic has five hundred patients on its books, some of whom, like Mrs Mary O’Halloran, have been coming to the clinic since it opened ten years ago.
Choose the type of stakeholder for each of the names listed in the box. Stakeholders:
? staff
? client
? supplier
Person Type of stakeholder
Peter Smith
Keith Dickson
Mrs Mary O’Halloran
Brian Huang
David Andrews
Pauline Santoro
Task 2 — Gantt chart
Use MS Project and draw a Gantt chart corresponding to the specifications in the table below, and also determine the milestone for this project.
Table : Gantt chart specifications
Task Staff Duration (Weeks) Budget
(1,000$) Prerequisites
Feasibility Study John, Jill 12 2
Analysis requirement Louise, Larry 8 0.5
Design solution Mark 5 2 Feasibility Study, Analysis
requirement
Develop system Jane, Jeff, Julie, James 10 5 Design solution
Software Development Methodologies – Assessment Task 1 LAST UPDATED: March 2018, Version No. 1.0

Testing
Brenda, Brad, Bella 10 1 Design solution
Deployment Tony 5 0.2 Develop system, Testing
Task 3 — Change negotiation
Case study
HAKME is undertaking a project (I-CUE, Intuitive Contacts, Updates and Enhancements) to update their contact management system. An issue has been raised by Bob Jenkison, customer relations manager, regarding the tracking and delegation of open cases. After reviewing the issue’s log, you determined that the change is currently outside the technical specifications of the project and a change request needs to be submitted and approved.
Peta Young, technical lead, has reviewed the issues log. She feels that it is too late in the development stage of the project to change the technical requirements and feels the customer is constantly shifting the project goals.
Review the emails below sent to you by Bob Jenkison and Peta Young outlining their stance on the issue and work out a strategy to best handle the situation.
From: Peta.Young@hakme.com.au
To: i-cue.project.manager@hakme.com.au
Subject: Issue number-1143 tracking and delegation of open cases
Hi there
I have looked at issue 1143 regarding the tracking of open customer cases for the I-CUE project. We have already passed the functional specification freeze and will be entering beta release in two weeks. We have come too far to change the functional specifications of the project. It feels like the customer keeps extending the scope of the project beyond what we can deliver. I think it is time to set boundaries.
I did a quick calculation and estimated that it would cost about $1,550,000 and 60 days to code for an email and task notification system or $850,000 and 40 days to code for an email-only notification system. This doesn’t include the extra cost of beta testing the extra modules and upgrading the capacity of the email system to cope with the extra workload. I strongly suggest we not implement a technical solution to this issue but rather tackle it through other means like a change in operating procedures.
Kind regards
Peta Young Technical Lead
Software Development Methodologies – Assessment Task 1 LAST UPDATED: March 2018, Version No. 1.0

From: Bob.Jenkinson@hakme.com.au
To: i-cue.project.manager@hakme.com.au
Subject: Issue number-1143 tracking and delegation of open cases
Hi there,
I have logged an issue regarding the tracking of open customer cases for the I-CUE project. This issue is important as it impacts on the company’s professionalism when handling customer cases. One of the major reasons we are losing customers is a lack of follow-up service, as was made known by a customer survey that we conducted five days ago. The outcome is that this is hurting our reputation and impacting the bottom line. To put this in money terms, for every customer we lose, we have to spend an average of $450 on advertising and promotion to gain a new customer or $1200 to regain a disgruntled customer. Last year alone we spent more than $850,000 to regain lost customers.
All I want is a reminder email sent to the case worker after five days of inactivity, warning them that the case has no actions recorded against it and, after eight days, a task request sent to the case worker’s supervisor requesting a follow-up. This could save the company thousands of dollars and - more importantly - improve our customer service reputation.
Kind regards
Bob Jenkison
Customer Relations Manager
Task 4 — Quality
Consider the Intuitive Contacts, Updates and Enhancements project (Task 3) for I-CUE. Who are the main quality stakeholders for the project?
Task 5 — Variance reporting
The I-CUE steering committee has requested a variances report outlining the impact of the recent change to the development phase of the project. Using the financial information provided, complete the “Variance Report” for the developing tasks.
Variance Report
Activity Name : Developing Date:

Task Name Plan Actual Variance
Software Development Methodologies – Assessment Task 1 LAST UPDATED: March 2018, Version No. 1.0

Update risk assessment
Equipment for development/proof of concept arrives Set up development environment/lab
Internal Release #1
Develop target components
Test individual components
Test integrated application
Develop performance enhancement materials
Test and review materials
Develop distribution procedures
Create distribution product
Distribute to appropriate parties
Buffer
Internal release #1 complete
Review results from internal release
Perform post-release review
Internal Release 2
Develop target components
Test individual components
Test integrated application
Develop performance enhancement materials
Test and review materials
Develop distribution procedures
Create distribution product
Buffer
Distribute to appropriate parties
Internal release 2 complete
Internal Release 3
Develop target components
Test individual components
Test integrated application
Develop performance enhancement materials
Test and review materials
Develop distribution procedures

Software Development Methodologies – Assessment Task 1 LAST UPDATED: March 2018, Version No. 1.0

Create distribution product
Buffer
Distribute to appropriate parties
Internal release 3 complete
Review results from internal release
Functional specification freeze
Final feature development
Final logistics development
Final performance support development
Feature complete
Update Plans and Schedules
Update development plan
Update testing plan
Update logistics plan
Update program management plan
Update product management plan
Update user education plan
Buffer
Perform milestone review
Scope complete

Software Development Methodologies – Assessment Task 1 LAST UPDATED: March 2018, Version No. 1.0

Table: Pre-change budgeted costs
Task Name Total Cost
Developing $1,999,532.00
Update risk assessment $492.00
Equipment for development/proof of concept arrives $0.00
Set up development environment/lab $4,800.00
Internal Release #1 $422,560.00
Internal release #1 complete $0.00
Review results from internal release $0.00
Perform post-release review $0.00
Internal Release #2 $424,960.00
Distribute to appropriate parties $4,480.00
Internal release #2 complete $15,680.00
Internal Release #3 $0.00
Distribute to appropriate parties $0.00
Internal release #3 complete $0.00
Review results from internal release $32,800.00
Functional specification freeze $0.00
Final feature development $104,000.00
Final logistics development $15,840.00
Final performance support development $7,600.00
Feature complete $0.00
Update Plans and Schedules $95,520.00
Buffer $49,200.00
Perform milestone review $32,800.00
Scope complete $15,680.00
Software Development Methodologies – Assessment Task 1 LAST UPDATED: March 2018, Version No. 1.0

Table: Post-change budgeted costs
Task Name Total Cost
Developing $2,951,052.00
Update risk assessment $492.00
Equipment for development/proof of concept arrives $0.00
Set up development environment/lab $4,800.00
Internal Release #1 $422,560.00
Internal release #1 complete $0.00
Review results from internal release $0.00
Perform post-release review $0.00
Internal Release #2 $424,960.00
Distribute to appropriate parties $4,480.00
Internal release #2 complete $15,680.00
Internal Release #3 $578,560.00
Distribute to appropriate parties $4,480.00
Internal release #3 complete $15,680.00
Review results from internal release $15,680.00
Functional specification freeze $0.00
Final feature development $104,000.00
Final logistics development $15,840.00
Final performance support development $7,600.00
Feature complete $0.00
Update Plans and Schedules $95,520.00
Buffer $49,200.00
Perform milestone review $32,800.00
Scope complete $15,680.00
Software Development Methodologies – Assessment Task 1 LAST UPDATED: March 2018, Version No. 1.0

Task 6 – Requirements specification
Case Study
Sharp Solutions has just employed a Database Marketing Consultant to assist the Marketing Team in targeting potential business. The consultant, Jacqui Rutherford, has asked for a database to be created to store details of existing clients and the software and hardware they have purchased from us.
A Systems Analyst has already designed and created the database tables, and you have been asked to develop a program that will allow the Marketing Team to update these tables and to identify clients whose software or hardware is over three years old.
The system/ software will also print details of these clients so they can be targeted in future marketing campaigns.
Sharp Solutions want their new application to reduce operational costs by $2,000 per year per staff member by reducing record processing time by 40%.
The organisation is only willing to spend $20,000 to add capability to its existing infrastructure but have a very broad time limit for this to be done.
Write the functional requirements of the program/software?
Task 7 – Standards document
Layout of the standards document of the s/w development project that you are working on (Task 6) is as follows
Standards Document Table of Contents
1.0 Introduction
2.0 Design Standards
2.1 interface Presentation
2.2 interface Layout
2.1 interface Support
3.0 Coding Standards
4.0 Object Naming Conventions
Describe what should be included in the highlighted section?
Task 8 - Quality Objectives
Which standard you should follow for the quality of the software you are going to develop? Also describe the characteristics of that quality standard.
Software Development Methodologies – Assessment Task 1 LAST UPDATED: March 2018, Version No. 1.0

Task 9 - Reviewing and reporting on implementation standard
A project plan has been developed for a theoretical project. The image below represents the project schedule. The project was segmented into the four phases: Initialising, Planning, Executing and Controlling.
? The Initialising phase involved a kick off meeting and development of a Project Charter.
? The Planning phase involved developing project plans, but importantly the plans were to be continuously reviewed and updated. This enabled the management of project compression or expansion.
? The Executing phase involved analysis, design and implementation. The design activity included scheduling for unit testing, system testing and user evaluation. The number of tests was directly related to the duration of the design. Implementation testing was to be a once-off activity, based on the approval of the design.
? The Controlling phase included five status reports and the continuous updating of performance reports. The project included a method for controlling changes. Changes were to be completed before implementation.
What should the Status Report 1 indicate based on the Gantt chart indicated below?

Task 10 - Acceptance criteria
Consider the s/w development project in Task 6.
What are the acceptance criteria you can think of by reflecting on the business requirements, functional requirements and technical specifications for the proposed s/w?
Task 11 - Software metrics
What are the metrics can be used to measure the performances of the software development project? How these metrics can be implemented?
Software Development Methodologies – Assessment Task 1 LAST UPDATED: March 2018, Version No. 1.0

Task 12 -Report milestones and metrics to ensure written agreement
Consider the following milestones and metrics for an s/w development project: Software Project Planning
1. Is software scope unambiguously defined and bounded?
2. Are resources adequate for scope?
3. Have risks in all important categories been defined?
4. Are tasks properly defined and sequenced?
5. Is the basis for cost estimation reasonable?
6. Have historical productivity and quality data been used?
7. Is the schedule consistent?
Requirements Analysis
1. Is information domain analysis complete, consistent and accurate?
2. Does the data model properly reflect data objects, attributes and relationships?
3. Are all requirements traceable to system level?
4. Has prototyping been conducted for the user/customer?
5. Are requirements consistent with schedule, resources and budget?
Design
1. Has modularity been achieved?
2. Are interfaces defined for modules and external system elements?
3. Are the data structures consistent with the information domain?
4. Are the data structures consistent with the requirements?
5. Has maintainability been considered?
Code
1. Does the code reflect the design documentation?
2. Has proper use of language conventions been made?
3. Have coding standards been observed?
4. Are there incorrect or ambiguous comments?
Testing
1. Have test resources and tools been identified and acquired?
2. Have both white and black box tests been specified?
3. Have all the independent logic paths been tested?
4. Have test cases been identified and listed with expected results?
5. Are timing and performance to be tested?
For business reasons, the s/w has been delivered without highlighted metrics being tested, but with the intention that the developer will complete, test and deliver the modification within an agreed time.
What are the possible actions can be taken for this situation?
Task 13 – Multiple Choice Questions
1) What is the structured approach called for developing software and information systems?
a) Software design
b) Prototyping
Software Development Methodologies – Assessment Task 1 LAST UPDATED: March 2018, Version No. 1.0

c) Systems development life cycle
d) Systems methodology
2) Who is the person who typically manages the software development project?
a) Software engineer
b) Project manager
c) IT manager
d) Technology director
3) In which phase of the software design and development project would you try to understand the proposed project?
a) Planning phase
b) Initial phase
c) Requirements phase
d) Analysis phase
4) What term refers to the fast-paced building or construction of a software prototype?
a) Rapid application development (RAD)
b) Rapid agility programming (RAP)
c) Speed programming
d) Express development (ED)
5) What type of software design and development methodology does Microsoft Corporation employ?
a) Rapid application development
b) Extreme programming
c) Speed programming
d) Express development
6) Which of these are standards for assessing software processes?
a) SEI
b) SPICE
c) ISO 9000
d) ISO 9001
e) both b and d
7) The waterfall model of software development is
a) A reasonable approach when requirements are well defined.
b) A good approach when a working program is required quickly.
c) The best approach to use for projects with large development teams.
d) An old fashioned model that is rarely used any more.
8) The incremental model of software development is
a) A reasonable approach when requirements are well defined.
b) A good approach when a working core product is required quickly.
c) The best approach to use for projects with large development teams.
d) A revolutionary model that is not used for commercial products.
9) The spiral model of software development
Software Development Methodologies – Assessment Task 1 LAST UPDATED: March 2018, Version No. 1.0

a) Ends with the delivery of the software product
b) Is more chaotic than the incremental model
c) Includes project risks evaluation during each iteration
d) All of the above
10) Which of the following is not one of the attributes of software quality?
a) Adds value for developers and users
b) Effective software process creates infrastructure
c) Removes need to consider performance issues
d) Useful products satisfy stakeholder requirements
11) Which of the following are ISO 9126 software quality factors?
a) Functionality
b) Portability
c) Reliability
d) Visual appeal
e) a, b, and c
12) The project plan should include explicit techniques for _______ and _______ management?
a) change
b) cost
c) error
d) quality
e) both a and d
13) The level of review formality is determined by which of the following?
a) amount of preparation
b) reviewer follow-up
c) size of project budget
d) structure of review
e) a, b and d
14) An informal review may consist of which of the following?
a) casual meeting
b) desk check
c) inspection
d) pair programming
e) both a and b
15) Which of the following are objectives for formal technical reviews?
a) allow senior staff members to correct errors
b) assess programmer productivity
c) determining who introduced an error into a program
d) uncover errors in software work products
16) At the end of a formal technical review all attendees can decide to a) accept the work product without modification
Software Development Methodologies – Assessment Task 1 LAST UPDATED: March 2018, Version No. 1.0

b) modify the work product and continue the review
c) reject the product due to stylistic discrepancies
d) reject the product due to severe errors
e) both a and d
17) A review summary report answers which three questions?
a) terminate project, replace producer, request a time extension
b) what defects were found, what caused defects, who was responsible
c) what was reviewed, who reviewed it, what were the findings
d) none of the above
18) Which of these are valid reasons for measuring software processes, products, and resources?
a) to characterize them
b) to evaluate them
c) to price them
d) to improve them
e) a, b, and d
19) Public metrics are used
a) to evaluate the performance of software development teams.
b) to appraise the performance of individual team members.
c) to make strategic changes to the software process.
d) to make tactical changes during a software project
e) both c and d
20) Which of following are advantages of using LOC (lines of code) as a size-oriented metric?
a) LOC is easily computed.
b) LOC is a language dependent measure.
c) LOC is a language independent measure.
d) LOC can be computed before a design is completed.
Task 14 – True-False Questions
1) Quality of conformance focuses on the degree to which the implementation of a design meets its requirements and performance goals.
2) Product quality can only be assessed by measuring hard quality factors.
3) Many software metrics can only be measures indirectly.
4) The quality dilemma might be summarized as choosing between building things quickly or building things correctly.
5) Good enough software delivers high quality software functions along with specialized functions that contain know bugs.
6) Poor quality leads to software risks that can become serious?
Software Development Methodologies – Assessment Task 1 LAST UPDATED: March 2018, Version No. 1.0

7) When a system fails to deliver required functions it is because the customer changes requirements?
8) Developers must start focusing on quality during the design phase in order to build secure systems.
9) Quality control encompasses a set of software engineering actions that help to ensure that each work product meets its quality goals.
10) The goal of quality assurance to insure that a software project is error free.
11) The purpose of software reviews is to uncover errors and defects in work products so they can be removed before moving on to the next phase of development.
12) In general the earlier a software defect is discovered and corrected the less costly to the overall project budget.
13) Review metrics can be used to assess the efficacy of each review activity.
14) Defect density can be estimated for any software engineering work product.
15) In any type of technical review, the focus of the review is on the product and not the producer.
Software Development Methodologies – Assessment Task 1 LAST UPDATED: March 2018, Version No. 1.0

Looking for answers ?


Recent Questions