Information Technology Project.
I need some help please.
A. Project Description: One of the objectives of this course (IT 281) is to acquire the practical skills needed in order to develop an information system (IS). To meet this objective, a group should be formed to carry out a term project. Depending on the class/section size, the size of the groups should be determined, this should be agreed with your lab instructor. This project should provide you, as a student, the opportunity to plan, analyse, and design an information system, which is intended to address a real-world problem, in other words, to fulfil a business need. To do that, you may need to find an organization that is willing to grant your team an access to its data or to apply the relevant suitable information gathering techniques, in order to gather the requirements and to inform the analysis and the design for the new IS. For instance, the proposed IS should be particularly designed to address a current lacking in that organization or to improve their current system somehow. Depending on the problem you are tackling by your proposed system (the solution), you may choose to design/develop a Website, Software component, or an application, etc. The activities to be carried out during this project should utilize materials learned throughout the course (activities, steps, modelling techniques, etc.), so it is recommended that you get an early start on forming your group and meeting weekly for this purpose. The system chosen should not be too big or too small; the marking emphasis will be on the accuracy of the requirements gathered and the final product thoroughness, NOT on its size. The main deliverable for the project will be in the form of a "systems proposal". So, the nature of the deliverable should be adjusted accordingly. Adhere to the 'Project Template' specifications for this purpose. Some examples for suitable projects, but not limited to the following: - A point-of-sales (POS) system - Inventory System - Payroll System Tou are expected to be strictly following the below project guidelines: - Project scope and ideas - In the appendix for this document, a list of the previous IT281 projects is provided. Use this list as a reference example. You MUST NOT re-choose any of the project that has been chosen in the 3 last preceding semesters. - The proposed IS should have, at least, 5 main identifiable functionalities (use cases). - Project activities and tasks The undertaking work for this project must be a team work. If the workload is unfairly divided or unbalanced among the members of the project team, it will be apparent during the discussion, the underperforming member, will be easily identified by the lab teacher and therefore his/her mark will be affected. - There will be no extension in the submission due dates. Milestone and due dates clarified on Table 1. - Work quality and originality The undertaken work for this project should be genuinely YOURS as a group. If any information or statements has been quoted or paraphrased from a scientific source, then the source should be properly cited and the whole references list should be provided at the end of the document. If so, use Harvard style (Author-date system). - Any project detected with any source of plagiarism (cheated content, adopting other people's work, non-original work) will be marked ZERO. - Be aware that LMS Blackboard uses plagiarism check tool! - Documentation No handwriting is accepted. Use the 'Project Template' file and adhere to its outlines and format ONLY. Make sure that the language used in your text is understandable, grammatically adequate and free from typo errors. Font to be used is Times New Roman, Size 12 point, applying 1.15 line spacing. Only black color font should be used. Don't forget to fill in your project title in the submitted copy, your section along with your team members' full names and students' IDs. - Modelling You can ONLY use (StarUml) tool to draw the required UML diagrams. Beside the details given in the following table (Table 1), the content of UML diagrams/models (depth and breadth) are as follows: - 1 Use-Case diagram for the main system (with at least 5 major use-cases) (avoid log in/log-out and contact-us use cases). - Use-Case FULL descriptions (at least 3 major use-cases). - Activity diagram for each use case, using SWIMLANES technique. - 1 detailed Class diagram (Attributes and Methods) - 1 Architectural Configuration diagram A. Project Description: One of the objectives of this course (IT 281) is to acquire the practical skills needed in order to develop an information system (IS). To meet this objective, a group should be formed to carry out a term project. Depending on the class/section size, the size of the groups should be determined, this should be agreed with your lab instructor. This project should provide you, as a student, the opportunity to plan, analyse, and design an information system, which is intended to address a real-world problem, in other words, to fulfil a business need. To do that, you may need to find an organization that is willing to grant your team an access to its data or to apply the relevant suitable information gathering techniques, in order to gather the requirements and to inform the analysis and the design for the new IS. For instance, the proposed IS should be particularly designed to address a current lacking in that organization or to improve their current system somehow. Depending on the problem you are tackling by your proposed system (the solution), you may choose to design/develop a Website, Software component, or an application, etc. The activities to be carried out during this project should utilize materials learned throughout the course (activities, steps, modelling techniques, etc.), so it is recommended that you get an early start on forming your group and meeting weekly for this purpose. The system chosen should not be too big or too small; the marking emphasis will be on the accuracy of the requirements gathered and the final product thoroughness, NOT on its size. The main deliverable for the project will be in the form of a "systems proposal". So, the nature of the deliverable should be adjusted accordingly. Adhere to the 'Project Template' specifications for this purpose. Some examples for suitable projects, but not limited to the following: - A point-of-sales (POS) system - Inventory System - Payroll System Tou are expected to be strictly following the below project guidelines: - Project scope and ideas - In the appendix for this document, a list of the previous IT281 projects is provided. Use this list as a reference example. You MUST NOT re-choose any of the project that has been chosen in the 3 last preceding semesters. - The proposed IS should have, at least, 5 main identifiable functionalities (use cases). - Project activities and tasks The undertaking work for this project must be a team work. If the workload is unfairly divided or unbalanced among the members of the project team, it will be apparent during the discussion, the underperforming member, will be easily identified by the lab teacher and therefore his/her mark will be affected. - There will be no extension in the submission due dates. Milestone and due dates clarified on Table 1. - Work quality and originality The undertaken work for this project should be genuinely YOURS as a group. If any information or statements has been quoted or paraphrased from a scientific source, then the source should be properly cited and the whole references list should be provided at the end of the document. If so, use Harvard style (Author-date system). - Any project detected with any source of plagiarism (cheated content, adopting other people's work, non-original work) will be marked ZERO. - Be aware that LMS Blackboard uses plagiarism check tool! - Documentation No handwriting is accepted. Use the 'Project Template' file and adhere to its outlines and format ONLY. Make sure that the language used in your text is understandable, grammatically adequate and free from typo errors. Font to be used is Times New Roman, Size 12 point, applying 1.15 line spacing. Only black color font should be used. Don't forget to fill in your project title in the submitted copy, your section along with your team members' full names and students' IDs. - Modelling You can ONLY use (StarUml) tool to draw the required UML diagrams. Beside the details given in the following table (Table 1), the content of UML diagrams/models (depth and breadth) are as follows: - 1 Use-Case diagram for the main system (with at least 5 major use-cases) (avoid log in/log-out and contact-us use cases). - Use-Case FULL descriptions (at least 3 major use-cases). - Activity diagram for each use case, using SWIMLANES technique. - 1 detailed Class diagram (Attributes and Methods) - 1 Architectural Configuration diagram
