7163MAA Project Management Information Systems Coursework 2 Assignment Brief | CU

 

7163MAA Assignment Task

You are you are tasked:

1) Apply the risk and stakeholder register for the case study
2) To properly implement a PMIS, you can use the analysis and suggestions to come up with a strategy to address any issues in the case.
3) Design a Database structure suitable for handling corporate customers’ records (Entity Relationship Diagram & Tables structure).

Team Engineers (Pvt.) Limited

In 1975, Ben Llewelyn began building computer equipment in a small garage behind his house. After 17 years, Team Engineers (Pvt.) Limited was transformed into a £1 billion firm generating a gross net worth per year through a manufacturing organisation, employing 900 people. The major success found by TE has been attributed to the non-degreed workers who have stayed with TE over the past fifteen years. The non-degreed personnel account for 80 per cent of the organisation. Both the salary structure and fringe benefit packages are well above the industry average.

CEO PRESENTATION: In February 1992, the new vice president and general manager made a presentation to his executive staff outlining the strategies he wished to see implemented to improve productivity: Our objective for the next twelve months is to initiate a planning system with the focus on strategic, developmental, and operational plans that will assure the continued success of TE and support for our broad objectives. Our strategy is a four-step process:

• To better clarify expectations and responsibility
• To establish cross-functional goals and objectives
• To provide feedback and performance results to all employees at each level of management
• To develop participation through teamwork

Synopsis

All projects at TE have project managers assigned and are handled through the Information Services Division (ISD). The organisational structure is not a matrix, although some people think that it is. The case describes one particular project, the development of a corporate database, and the resulting failure. The problem at hand is to investigate why the project requires system improvement.

CW2 (10 Credits)

The assignment is to be submitted as a single submission per group of up to 3000 words (+/- 10%) composed of a report and the developed registers and database structure (using any database of your own choice). Submissions will be judged on the completeness, quality, and functionality of the design, in addition to the critical analysis of all elements and components contained within, their alignment with the case study, and the use of supporting academic literature and industrial best practices in the provided explanations.

Submission Instructions:

1. Your Report should include:

a. Cover page with:
i. Module code & title
ii. List of Student Names & SID

b.Table of content / List of figures/Tables (if present)
c.Diagrams and any other relevant detail of your approach
d. Your analysis of the case

i. Stakeholders’ analysis
ii. Risks analysis
iii. Failure analysis/Situation analysis

e. Your suggestions and recommendations on how the project should have been managed

f. The description of your suggested solution (as per implementation you will submit)

2. Your implementation should include:

a. Risk register
b. Stakeholders’ register
c. Database structure:

i. Entity Relationship Diagram (ERD)
ii. Database tables (empty)

3. The submission file MUST respect the following characteristics:
a. Name: 7163MAA-2425-Gxx.doc (for the report)
b. Name: 7163MAA-2425-Gxx.Zip (for the implementation)

4. The submission will be done using:
a. Turnitin (report ONLY one submission per group)
b. Handin (implementation: ONLY one submission per group).

You are supposed to demonstrate your understanding of the module and meet the learning outcomes by producing documents that are professionally presented and checked for quality.

Special Note

The following are some essential requirements for delivering this assessment successfully:

1. You will be supported by a Mentor.
2. The manual is expected to have a professional presentation (quality/professionally designed materials with valuable contents that reflect team preparation)
3. Your manual should be structured as indicated.
4. Marks will be awarded for a suitable layout and acceptable use of business English.
5. Only one combined submission per team.
6. Lastly, pay attention to the Marking Scheme provided here in the appendix.

Coursework (Summative) Marks Distribution

LO	Description	Mark
LO4	Apply the principles of information management in an organization or project. •   Understand the customer’s needs (supported by clear explanation) •   Select the PMIS level that corresponds to the complexity of the provided case (justification required) •   Devise the development approach and structure for the creation of the best Risk/Stakeholder registers for the proposed case study •   Devise the testing and evaluation approach to be used	30
LO5	Design the information management for an organization or project. •   Design and structure the PMIS in an efficient and effective way (coverage) •   Implement and test the proposed structure with reasonable data •   Simulate the usage of the devised registers and evaluate their performances	65
LO4-5	Academic writing •   Correct use of the language with adequate use of technical terms •   Professional structuring and presentation of the manual	5
		100

General Notes:

1. You are expected to use the APA referencing format. For support and advice on how this works students can contact Centre for Academic Writing (CAW).

2. Please notify your registry course support team and module leader for disability support.

3. Any student requiring an extension or deferral should follow the university process as outlined here.

4. The University cannot take responsibility for any coursework lost or corrupted on disks, laptops or personal computer. Students should therefore regularly back up any work and are advised to save it on the University system.

5. If there are technical or performance issues that prevent students from submitting coursework through the online coursework submission system on the day of a coursework deadline, an appropriate extension to the coursework submission deadline will be agreed. This extension will normally be 24 hours or the next working day if the deadline falls on a Friday or over the weekend. This will be communicated via your Module Leader.

6. You are encouraged to check the originality of your work by using the draft Turnitin links on your AULA Web.

7. Collusion between students (where sections of your work are similar to the work submitted by other students in this or previous module cohorts) is taken extremely seriously and will be reported to the academic conduct panel. This applies to both coursework and exam answers.

8. A marked difference between your writing style, knowledge and skill level demonstrated in class discussion, any test conditions and that demonstrated in a coursework assignment may result in you having to undertake a Viva Voce to prove the coursework assignment is entirely your own work.

9. If you make use of the services of a proofreader in your work, you must keep your original version and make it available as a demonstration of your written efforts.
 
10. You must not submit work for assessment that you have already submitted (partially or in full), either for your current course or for another qualification of this university, unless this is specifically provided for in your assignment brief or specific course or module information. Where earlier work by you is citable, i.e. it has already been published/submitted, you must reference it clearly. Identical pieces of work submitted concurrently will also be considered to be self-plagiarism.

Remember:

Academic Offences

When writing any form of essay or academic assignment, you will often need to support your arguments by referring to other published works such as books, peer-reviewed journals or newspaper articles, government reports, dissertations and theses, and material from the Internet. You will need to give accurate references:

• To give credit to other authors’ concepts and ideas
• To provide the reader (often the marker/examiner of the assignment) with evidence of the breadth and depth of your reading
• To enable the readers of your work to locate the references easily
• To avoid being accused of plagiarism, an academic offence which can lead to loss of marks, module failure or in severe cases exclusion from the University.

Academic Offences

Academic offences, including plagiarism, incur a very severe penalty in Coventry University. Any student who is proven to have committed an academic offence may be placing his or her degree in jeopardy. It is your responsibility as a student to make sure that you understand what constitutes an academic offence, and in particular, plagiarism and how to avoid it.

Development of Skills and Attributes

The Graduate Attributes being developed in this assessment are:

• Act with integrity by working effectively as a team member.
• adapt approach; by reaching consensus on how to deliver a solution as a group.
• think creatively, by researching and delivering an effective solution to a real-world problem.
• get things done. By delivering your element of the project on time and you enable other team members to work effectively.

7163MAA Marking and Feedback

How will my assignment be marked?

Your assignment will be marked by the module leader.

How will I receive my grades and feedback?

Provisional marks will be released once internally moderated.
Feedback will be provided via documents uploaded into the Aula hand-in.
Your provisional marks and feedback should be available within 2 weeks (10 working days) after the final submission is done.

What will I be marked against?

Details of the marking criteria for this task can be found at the bottom of this assignment brief.

7163MAA Assessed Module Learning Outcomes

The Learning Outcomes for this module align with the marking criteria, which can be found at the end of this brief. Ensure you understand the marking criteria to ensure achievement of the assessment task. The following module learning outcomes are assessed in this task:

4. Apply the principles of information management in an organisation or project.
5. Design the information management for an organisation or project.

Assessment Marking Criteria

Criterion		Excellent (70-100)	Very Good (60-70)	Good (50-60)	Pass (40-50)	Fail (39-0)
LO4	Understand the customer’s needs (supported by clear explanation)	Extremely well and clearly understood customer’s needs critically analysed and discussed (very well supported by literature)	Very well and clearly understood customer’s needs critically analysed and discussed (well supported by literature)	Well and clearly understood customer’s needs critically analysed and discussed (supported by literature)	Acceptably understood customer’s needs analysed and partially discussed (partially supported by literature)	Poorly understood customer’s needs not sufficiently analysed and poorly partially discussed (not supported by literature)
	Select the PMIS level that corresponds to the complexity of the provided case (justification required)	The PMIS level selection is excellent in terms of justification and correspondence with the complexity of the provided case	The PMIS level selection is very good in terms of justification and correspondence with the complexity of the provided case	The PMIS level selection is good in terms of justification and correspondence with the complexity of the provided case	The PMIS level selection is acceptable in terms of justification and correspondence with the complexity of the provided case	The PMIS level selection is not acceptable in terms of justification and correspondence with the complexity of the provided case
	Devise the development approach and structure for the creation of the best Risk/Stakeholder registers for the proposed case study	Extremely well designed and implemented development approach and structure for the creation of the best Risk/Stakeholder registers for the proposed case study	Very well designed and implemented development approach and structure for the creation of the best Risk/Stakeholder registers for the proposed case study	Well designed and implemented development approach and structure for the creation of the Risk/Stakeholder registers for the proposed case study	Acceptably designed and implemented development approach and structure for the creation of the Risk/Stakeholder registers for the proposed case study	Poorly designed and implemented development approach and structure for the creation of the Risk/Stakeholder registers for the proposed case study
	Devise the testing and evaluation approach to be used	Extremely well designed and implemented testing and evaluation approach used to validate the implemented Risk/Stakeholder registers for the proposed case study	Very well designed and implemented testing and evaluation approach used to validate the implemented Risk / Stakeholder registers for the proposed case study	Well designed and implemented testing and evaluation approach used to validate the implemented Risk/Stakeholder registers for the proposed case study	Acceptably designed and implemented testing and evaluation approach used to validate the implemented Risk/Stakeholder registers for the proposed case study	Poorly designed and implemented testing and evaluation approach used to validate the implemented Risk/Stakeholder registers for the proposed case study
LO5	Design and structure the PMIS in an efficient and effective way (coverage)	Excellent design and structure for the PMIS with an excellent, efficient and effective coverage	Very good design and structure for the PMIS with an excellent, efficient and effective coverage	Good design and structure for the PMIS with an excellent, efficient and effective coverage	Acceptable design and structure for the PMIS with an excellent, efficient and effective coverage	Poor design and structure for the PMIS with an excellent, efficient and effective coverage
	Implement and test the proposed structure with reasonable data	Excellent implementation and testing of the developed structure with reasonable data	Very good implementation and testing of the developed structure with reasonable data	Good implementation and testing of the developed structure with reasonable data	Acceptable implementation and testing of the developed structure with reasonable data	Poor implementation and testing of the developed structure with reasonable data
	Simulate the usage of the devised registers and evaluate their performances	Excellent simulation of the implementation of the devised registers and evaluation of their performances / functionalities	Very good simulation of the implementation of the devised registers and evaluation of their performances / functionalities	Good simulation of the implementation of the devised registers and evaluation of their performances / functionalities	Acceptable simulation of the implementation of the devised registers and evaluation of their performances / functionalities	Poor simulation of the implementation of the devised registers and evaluation of their performances / functionalities
Academic writing	Correct use of the language with adequate use of technical terms	Excellent usage of the technical terminology and mastery of the language	Very good usage of the technical terminology and mastery of the language	Good usage of the technical terminology and adequate mastery of the language	Acceptable usage of the technical terminology and adequate use of the language	Poor usage of the technical terminology and inadequate use of the language
	Academic structuring and presentation of the manual	Logically structured and very well written practical business manual produced in professional format	Logically structured and well-written business manual in professional format	Logically structured and written business manual in professional format	Logically structured and written manual in professional format	Unstructured and badly written manual lacking professional form