We write, we don’t plagiarise! Every answer is different no matter how many orders we get for the same assignment. Your answer will be 100% plagiarism-free, custom written, unique and different from every other student.
I agree to receive phone calls from you at night in case of emergency
Please share your assignment brief and supporting material (if any) via email here at: [email protected] after completing this order process.
100% Pass and No Plagiarism Guaranteed
Overview
This case study simulates a project management scenario where the student takes on the role of project manager. Students are required to use Microsoft project management software as part of this assessment task.
This is a group assignment with a maximum of three members per group. However, note that all members are also expected to attempt all parts of the assignment individually as assessment item sub-deliverables 1- 5. Members of the group are required to submit their own individual attempt for each of the sub-deliverables in Moodle before the group meets to consolidate answers to produce the "group solution". There are separate submission areas and due dates for the individual submissions . On time submission of the 5 sub-deliverables is worth a total of 5 marks, but these submissions may also be used to assess individual contributions and may impact on a student’s final mark.
Groups must meet at least once a week to produce the “group solution” for the work scheduled for completion in that week. This solution should then be added to the developing final group solution.
It is also important to meet early in week 10 to produce the updated schedule to be used to complete the Part C questions and status report. Each group is responsible for providing their own status data. This means that the group members must collaborate on this and ensure that all members are working with the same GD_PartC.mpp file when completing the Part C questions. This is explained further in part C.
There is one final group solution to be submitted at the end of the assignment. It is worth 35 marks and is to be submitted by only one member of the group. The names and student ids of all members of the group must appear clearly on the coversheet of the final assessment submission.
Peer assessment and your individual submissions will also be used to assess group member contributions. If any member of a team is not contributing satisfactorily to the group then he/she may have marks adjusted and/or be asked to leave the group and be required to complete the assignment as an individual.
If you are having difficulties within your group you must alert your tutor/lecturer as early as possible.
To assist students in their assessment solution development the following information is provided:
Where necessary, students are expected to find relevant information in the academic literature to justify their answers. Students may have to make assumptions and argue the pros and cons for any recommendations that they make. Any assumptions made must be clearly documented in the answers.
Great Devices is a medium sized company that develops and manufactures medical devices. You are an employee of Great Devices and work as project manager in the product development department. The people involved in this case study are:
You have been leading a small team of experienced engineers conducting a technical feasibility study to investigate if it is possible to modify one of the company’s standard products to create a product variant to satisfy the needs of veterinarians. You are planning to hold an M1 Milestone Concept Review on Friday the 20th May 2016. (For the purposes of this assignment assume that this is next week.) Assume that the start date of the project will therefore be Monday 23rdMay 2016 and that this is the date for the M1 milestone. The project management milestone concept review checklist is provided as Appendix 1. The concept review is one of the milestones in the company’s product development process.
The need for the new product has been identified by the marketing department lead by Ms. Douglas, Director of Marketing and Portfolio Management. Ms. Douglas provided your small project team with a product brief, outlining the special end user, sales and service requirements to supplement the requirements already established for the standard product. She also developed the business case for the product.
Your team has come up with a unique novel product concept that you believe should be protected by a patent. The concept satisfies the need perfectly. The feasibility work carried out with a user focus group showed that the user requirements were sound and that the technical complexity of the development was medium to low.
2.2 Milestones
The milestones your team will use are:
2.3 Initial Data
The system architecture of the product has been used as the basis for the project organisation and the work breakdown structure. As the project manager you have accepted the tasks of creating the compiled project schedule and allocating resources.
You have obtained the following information:
Note that the following resource abbreviations are used:
Table 1- Work Breakdown Structure
Activity
Description
Predecessor(s)
Resource and
To be
duration Estimates
completed
(in person-weeks)
before the
review
prior to
milestone
1.
Electronics
1.1 PWB outline modifications
Modifications required in
M1
1 person-week of
existing product for new
EE.
product
1.2 Component selection
Selection of electronic
1.1
2 person-weeks of
M2
components. Should be
started together with 1.3.
1.3 P1 circuit design and PWB
Creation of circuit diagram
layout
and PWB layout. Breadboard
solution created. Should be
started together with 1.2.
1.4 P1 electronics verification
Electronic verification tests
1.3, P1 build
2 person-week of
tests
with the use of the P1
complete (5.5)
prototypes.
1.5 P2 circuit design
Electronic improvements to
1.4
P2
improvements
circuit diagram, component
selection and layout.
1.6 P2 electronics verification
1.5, P2 build
M3
with the use of the P2
complete (6.5)
one EE.
1.7 Thermal verification tests
Verification that electronic
1.5 , P2 build
heat generation and heat
transmission through covers
is acceptable.
1.8 EMC verification tests
Verification of compliance
1.7
with electromagnetic
compliance regulations.
2.
Software
Page | 5
2.1 Software specification
Specification of the software
3 person-week of
functionality based on user
SE.
requirements.
2.2 Software and database
Design software and database
2.1
3 person-weeks of
design
SE
2.3 User interface development
Software additions due to
M2,2.2
modified menus and
functional keys.
2.4 Database development
Software additions to the
M2, 2.2
device database.
2.5 Development of device to
PC interface
communication protocol
between the device and the
PC.
2.6 Development of PC software
2.4,2.2
additions/modifications to the
PC software functionality to
support the new device
functionality.
2.7 R1 release creation
Creation of the R1 (release 1)
2.3, 2.4,
3 person-days of
software for testing
2.5,2.6
one SE.
2.8 R1 release tests
Testing of the R1 release and
2.7
identification of errors.
2.9 R1 error correction and
Creation of the R1 software
2.8
P1
user interface
release to be used with the P1
prototype.
2.10 R1 testing with prototype
Testing of the R1 software
Prototype 1
1
with the first prototype
build
complete
(5.5), 2.9
2.11 Documentation
Development of user and
2.10
4 person-weeks of
technical documentation
TW
manuals
2.12 R2 modifications
Modifications to the software
after testing with prototype 1
2.13 R2 release creation
Creation of the R2 software
2.12
2 person-days of
release to be used with the P2
2.14 R2 release tests with
Testing of the R2 release with
2.13,
prototype 2
prototype 2 and identification
Prototype
of errors.
build 2
2.15 R2 error corrections
Correction of errors
2.14
2.16 R2 interoperability tests
Testing of interoperability
2.15
with 3rd party accessory
devices.
2.17 R2 interoperability error
R2 interoperability error
2.16
correction
2.18 Finalise documentation
Finalise documentation
2.16, 2.11
including interoperability
information
2.19 R3 release creation
Creation of the R3 software
2.17
release.
2.20 R3 tests and corrections
Testing (and correcting) of
2.19
the R3 release
2.21 R4 sales release creation
Creation of the R4 software
2.18,2.20
sales release
3.1 Industrial design
Design of the industrial
design for the device.
ME/industrial
designer.
3.2 PWB outline modifications
Modifications of the PWB to
3.1
fit the industrial design, new
ME.
components and usability
Page | 6
3.3
P1 mechanical CAD design
CAD design of mechanical
3.2
plastic parts and metal parts
for the device.
3.4
Tolerance stack analysis
Analysis of the mechanical
tolerance stacks compared to
part tooling and moulding
capabilities.
3.5
P1 mechanical part analysis
Physical analysis of moulded
P1 build
plastic parts and sheet metal
parts.
3.6
P2 mechanical part
Modification of moulding and
modifications
sheet metal tools used for P2
3.7
Mechanical tool approval
Evaluation of P2 mechanical
P2 build
parts and approval of
moulding and sheet metal
tools used in part
manufacture.
4.1
Test plan creation
Creation of a plan
documenting what is to be
TE.
tested.
4.2
Component tests
Test of key component
After delivery
reliability to various standard
of components
TE
tests like drop and humidity.
(for P1 – i.e.
5.1) , 4.1
4.3
Module tests
Test of module functionality
after assembly.
(5.5), 4.2
4.4
System integration tests
Test of integration of
modules.
4.5
Product validation tests
Test of “final/prototype 2”
4.4, P2 build
product against reliability to
complete(6.5)
various standard tests like
drop and humidity and end
user requirements.
4.6
Technical Construction File
Creation of documentation
compilation
for regulatory approvals.
4.7
Type approval and regulatory
Approvals from regulatory
4 weeks by the
approval tests
authorities.
regulatory
authorities (not one
of the project team
resources). This is
a
“Fixed duration”
specified by the
authorities..
Notes:
Figure 1 - Activity in Box Network Diagrams for Production
P1 component lead-time
P1 prototype build
5.1
Suppliers
4w
5.5
Production
3d
Engineer
P1 PWB manufacture and delivery
5.2
Supplier
3w
P1 mechanical part lead-time
5.3
2w
P1 assembly and production test preparation
Hint: Remember that the
R1 software is also required for the P1 prototype build go/no-go review (see previous table)
5.4
P2 component lead-time
P2 prototype build
6.1
6.5
P2 PWB manufacture and
delivery
6.2
R2 software is also
P2 mechanical part lead-time
required for the P2
&l
International House, 12 Constance Street, London, United Kingdom, E16 2DQ
UK Registered Company # 11483120
View our samples written by our professional writers to let you comprehend how your work is going to look like. We have categorised this into 3 categories with a few different subject domains
If your assignment is plagiarised, we will give you £ 2999 in compensation
Jan,03,2025
