Statement Assignment Help
This document outlines what you have to submit to complete the project. It contains information about what you need to submit to your lecturer and what needs to be given to your client.
The things you need to deliver include computer programs (source code and executable code), database and/or data files, any documents associated with the system from this stage of the project (testing documentation, user manuals, installation guides, etc). The programs should be operational, free from errors, typos, misspelling, etc. The documents should be the most up-to-date to match the programs and data structure(s). You should prepare a document for handover of the product to the client. You should deliver the product to the client, and submit the product, the handover document, and your timeline and individual log book(s) to the supervisor. All the work should be professionally presented and the files should be organized properly.
Source code and executable code must be appropriately organized and must adhere to appropriate naming and formatting standards.
- Software Documentation
Software contains all documentation associated with the system product, including software requirements specification (SRS) and system design specification (SDS). These documents should be updated, if the final product varies from early versions of the documents
- Client Documentation
Training documentation should match the application and provide the user with a comprehensive and easy to use training manual. You are advised to read relevant sections of IEEE Std 1063-2001* for the composition of user documentation.
Implementation and handover documentation should be concise and clear. The document normally includes the name of the project, developer and client, handover date, a brief description of the product, a detailed list of deliverables, implementation details, remaining tasks if any, acceptance of the product by the client, and signatures of the developer and client. A specific project may include other specific details in the document. For example, if you have developed a website in the project, you should include the url of the website. You may need to include intellectual property statement in the document. For example, the client may be the owner of the product, or may be allowed to use a copy of the product, depending on your initial negotiation with the client.
You should submit a zip file by email to your supervisor, containing
- A Word document to describe your assignment, including
- an assignment cover sheet,
- a brief description of the assignment,
- details of deliverables and corresponding file names,
- instruction of installing the system in supervisor’s computer**
- other necessary details for your final product.
- Implementation and handover documentation
- Software product, including
- source code (both files of original format and pdf format),
- executable code,
- data files and/or database(s),
- image and content files,
- software documentation,
- training documentation, and
- other necessary components of the software product, for example installation program
- Project management documentation, including
- updated timeline, and
- updated individual work log books
You should arrange the files in proper folder structure*** in the zip file.
If your files are too large to send by email, you should inform your supervisor and post a CD or DVD to him or her.
- Marking Criteria
Final Product will be marked according to the criteria below unless otherwise discussed with and agreed to by your supervisor.
An external link to this standard is provided at MySCU.
You may need to discuss with your supervisor for details.
You should consider the ease of finding or use of the files. For example, it is not easy to find the design document if it is in the same folder that also contains image and content files.