1.0 Coursework Title
Electrical Installation and Inspection Management System (EIIMS)
2.0 The Coursework Overview
INSPECT-RICALS is a small electrical contracting company whose principle business area concerns domestic electrical wiring and installation. The firm mainly focuses upon condominium developers and owners, providing an installation and inspection service to ensure the safety of all electrical wiring within an apartment. INSPECT-RICALS are called to inspect both new developments as well as older apartments, with the latter taking place on a yearly basis. The firm requires a system to help facilitate and manage the inspection process, as well as produce the necessary reports for the benefit of management and clients. The intended users of the system are administrators, engineers and managers.
In addition to a working system which provides the necessary functionality, the firm is a strong proponent of the object oriented paradigm and therefore has stipulated that the system be developed using object oriented programming concepts.
3.0 Objectives of this Coursework
Develop the practical ability to describe, justify and implement an object-oriented system.
Research and present a contemporary object oriented topic
4.0 Learning Outcomes
At the end of this coursework you should be able to: • Understand the techniques of object oriented design • Develop hands on programming skills in developing Java applications • Design and implement object oriented software systems • Select appropriate object oriented techniques to solve software development problems
5.0 Type
Individual assignment
6.0 Coursework Description
INSPECT-RICALS engineers engage in two kinds of activity, new electrical installations and periodic inspection. The latter is a full inspection of a property's existing electrical wiring and appliances, and is usually a follow up to a previous inspection or installation. A new electrical installation involves the installation of new electrical wiring at a property for either an existing or new client. Upon completion of an electrical installation or a periodic inspection a detailed report verifying the inspection must be completed and issued to the person ordering the work
Customers contact the firm for either a new installation or for an inspection. The firm's clerk is responsible for all customer liaisons and will create a new customer account if the customer is a new customer. Details of the work are to be recorded into the system, such as whether it is an installation or an inspection. The clerk will then record the details of the property at which the inspection/installation is to take place (location, time/date, number of rooms, types of appliances etc). Upon creating the order the clerk allocates an engineer to the order. Engineers are to use the system for two purposes. Firstly, they will log in and view a list of all inspections (location, time/date etc) for the upcoming week. In addition, the engineers will use the system to generate a report regarding the work carried out, such as which appliances were tested etc. This will then be emailed to the client as proof of the inspection and installation, as well as printed and signed by the engineer in order to provided the client with a hard copy.
A record of the inspection will also be saved by the system and at the end of each week the clerk will collate all the completed inspections/installations and generate an invoice for each client. The management of the firm will primarily use the system for analysis purposes and intend to generate statistics, such as the number of inspections carried out and the amount of work done by each engineer.
There are four users of the system: The system administrator who will have full administrative access to the system, including user management and other settings.
A clerk who is responsible for customer and order management as well as responsible for allocating engineers to specific jobs. Engineers who are responsible for carrying out the inspections/installations and management who have full access to the system other than user management rights. The system must therefore be able to differentiate between these four types of users through the authentication and authorisation of users based on their specific job roles.
7.0 General Requirements
The program you submit should be able to execute without errors. In addition, all user input should be validated in order to minimise user errors. The implementation code must highlight the use of appropriate object oriented programming concepts as required by the solution. As the system requires persistent data all information which is entered or edited must be saved within text files. This is to ensure that the information can be retrieved at a later date.
8.0 Deliverables • The Installation/Inspection Management System with complete source code must be submitted in the form of a CD
• Documentation must be provided in printed and soft copy format
• Submission deadline:
8.1 Installation/Inspection Management System and Research Findings in CD format: The completed application/system as well as the soft copy of the report must be saved to a CD The application/system must contain all the relevant source code
8.2 Documentation: Coursework Report As part of the assessment you must submit the project report in printed and soft copy form. The report should follow the following structure: A) Cover Page: All reports must be prepared with a front cover. A protective transparent plastic sheet can be placed in front of the report to protect the front cover. The front cover should be printed with the following details: ■ Module ■ Coursework Title ■ Intake ■ Student name and id ■ Date Assigned (the date the assignment details were handed out). ■ Date Completed (the date the report is due to be handed in).
B) Contents: ■ Description and justification of the design involving • use case • activity diagram • analysis and design class diagram • the implementation code which illustrates the object oriented programming concepts incorporated into the solution ■ A 2000-word report based on the research done on the object oriented topic
C) Conclusion: Overall conclusions about your work, the system, the problems faced and the lessons learnt.
D) References ■ You may look for algorithms and information from the Internet or books. Proper referencing of the resources should be provided. ■ All references must be made using the Harvard Naming Convention as shown below: The theory was first propounded in 1970 (Larsen, A.E. 1971), but since then has been refuted; M.K. Larsen (1983) is among those most energetic in their opposition……….
/** * Following source code obtained from (Danang, S.N. 2002) */ int noshape=2; noshape=GetShape(); ■ List of references at the end of your document or source code must follow the following format Larsen, A.E. 1971, A Guide to the Aquatic Science Literature, McGraw-Hill, London. Larsen, M.K. 1983, British Medical Journal [Online], Available from http://libinfor.ume.maine.edu/acquatic.htm (Accessed 19 November 1995) Danang, S.N., 2002, Finding Similar Images [Online], The Code Project, *Available from http://www.codeproject.com/bitmap/cbir.asp, [Accessed 14th *September 2006] Further information on other types of citation is available in Petrie, A., 2003, UWE Library Services Study Skills: How to reference [online], England, University of Western England, Available from http://www.uweac.uk/library/resources/ general/info_study_skills/harvard2.htm, [Accessed 4th September 2013].
9.0 Assignment Assessment Criteria The assignment assessment consists of three components: Program Solution and Documentation (60%), Research Report (30%) and Presentation (10%). Details are as follows:
|Program Solution and Documentation (60%) |Research Report (30%) |
|Criteria |Marks Allocated % |Criteria |Marks Allocated %|
|Program Solution: Performance as per |30 |Structure of the report and references |10 |
|requirements | | | |
|Program Documentation: Description and |30 |Contents: |20 |
|justification of the design which | |Depth of the research | |
|incorporated object oriented programming | |Relevance of the research | |
|concepts | |Discussion of ideas | |
|Presentation (10%) |
|Ability to answer questions addressed by the lecturer pertaining to work done and presented |10 |
10.0 Development Environment The program must be created using the Java programming language. You can use any Java development IDE to do this.
11.0 Academic Integrity • You are expected to maintain the utmost level of academic integrity during the duration of the course. • Plagiarism is a serious offence and will be dealt with according to APIIT and Staffordshire University regulations.
