Report Characteristics for Enterprise Systems Students
Relevance Report
1. Clear definition of project and the related project domain.
This includes a clear identification of the project and the domain.
The team would need to identify the domain of the project. Here the domain refers to type of industries. For example, if the project is related to healthcareindustries,then the domainis healthcare. The team is expected to understand how similar problems have been solved in the research domain by answering questions such as:
- The existing systems used in the domain
- The benefits of existing systems in the identified domain
- The challenges of existing systems in the identified domain
- The new system to be implemented in the domain, if applicable
2. Clear definition of problem, which includes stakeholder analysis and/or user cases.
This section should address should address following important points:
1. First part should clearly outlines the Information/Enterprise Systemsproblem/ research question that this project is designed to address or answer. A research/project problem can be defined as an obstacle/issue that hinders organisation from the accomplishments of certain anticipated objectives.
A research question is normally inspired by some desire to investigate or explore something and necessarily assume some context. Therefore, while defining a research question for the project, both of these concepts should be clearly explained. The project team task should find out the appropriate answer to the research question/s.
2. Second part should clearly outlines the objectives for the project. These objectives should provide the client some kinds of benchmark against which the success/failure of the project can be evaluated.
3. The final part should identify the stakeholders who would be important to address the project problem that has been discussed in Part 1. Students are expected to justify each stakeholder listing.
3. Identification of different theories that support analysis/evaluation/ design and development/models/framework in the related domain and how it can be applied in the given project.
This includes an identification of different theories that support analysis/evaluation/ design and development/models/framework in the related domain and how it can be applied in the given project. Examples include TAM (Technology Acceptance Model) and Organization learning theories.
4. Problem related investigation about infrastructure/technology of the system to be studied.
The team have to do exhaustive research on the technology/infrastructure in question. This may include:
- Databases
- Application platform
- ERP modules
- Decision making software
- Data analytical tools
5. Description of existing approaches that can be applied in the current project.
This includes a discussion of the methodological approach for solving the research problem
The team is required to do a review of research methodologies relevant for investigating the identified problem. Data collection and analysis approaches previously used in investigating such problems as identified in 2 above should be discussed. Some of the possible topics of research are given below:
- Requirement gathering methods
- Data gathering methods
- Data analysis methods
The research should be in-depth in such a way that you should be able to substantiate your claim (in Project Report)when choosing any of the above methods.
6. Description of related and standard artifacts produced in similar projects
The team have to do exhaustive research on meta-artifacts produced in similar projects. The artifacts can be any (not limited) of the following:
- Project Management plan
- Post-implementation review document
- Training Manual
- Maintenance plan
- Project report for clients, including a description of lessons learned
- Data analysis report and charts
The research should be in-depth in such a way that you should be able to substantiate your claim (in Project Report) when choosing any of the artifacts to be developed during your project.
Project Report
1. Project execution plan based on the timeline defined in the Project 2.
Based on the research carried out in the Relevance report(especially in (4) and (5)), the team would have to prepare the project execution plan for ITECH 7405. In ITECH 7403 the ES teams would have to complete the problem investigation and analysis, while the development of artifact should be carried out in ITECH 7405.
2. Description of theories that support analysis/evaluation/ design and development/models/framework in the related domain and how it can be applied in the given project.
The description of theories should cover all relevant aspects comprehensively, and should be his includes an identification of different theories that support analysis/evaluation/ design and development/models/framework in the related domain and how it can be applied in the given project.
Using scholarly journal papers, peer-reviewed conferences, and relevant industry reports and articles, the identified theories/models/framework to be applied for the project must be justified.
3. Description of tools and techniques selected for (2).
This includes an in-depth discussion of the methodological approach for solving the research problem with 1 or 2 page justification.
The selection of specific data gathering and analysis tools and techniques to be applied for the project should be explained. Examples include Design science approach, case studies, surveys, etc. The team has to list the selected tool and techniques and give detailed description about how it will be applied for the project.
4. Description of artifacts that will be produced based on the Project 2 timeline.
The team has to come up with list of artifacts to be produced for the project and it should be consistent with the timeline for ITECH 7405. Please note - the problem analysis and project plan, including the description of artifacts to be produced during the project are to be completed in ITECH 7403. This description should be in-depth in such a way that you should be able to justify your choice of the artifacts, in 1 or 2 page, to be developed during your project.
5. Selected Testing and/or Evaluation Strategies.
The artifact produced should be tested or evaluated. The team would have to describe what evaluation strategies would be adopted to assess the suitability of the produced artifact. Justification of evaluation strategies should be documented.
ZNZ Education Student's Information System
1 Introduction
ZNZ Education is an organization that offers educational support services to overseas students'. The company uses manual process in updating and accessing their students'information. The company's sales and marketing departments are the most affected with these issues since they operate for both internal and external business transactions, therefore keeping track of these records is vital to them. After the interview with the client - ZNZ, the proponents have identified some key issues.
- The company is using an Excel spreadsheet as their electronic database of which the receptionist input the students' information such as full name and contact details. As per database spreadsheet it has limited capabilities in sorting and takes time to find records.
- ZNZ's sales department is associated with counsellors or consultants. The company regard its counsellor transaction with students because it is vital to them to keep track the record of which student they have handled or to be assigned to a new counsellor according to their acquired services it involves with sales commission basis as per counsellors transactions specially with new clients.
- ZNZ sales staff should repeat asking the existing client information in order to pull out their records therefore it is time consuming.
- Marketing department does not have a definite record how many students' from different levels are being served by their company from previous to current months.
- ZNZ had issues on disseminating information to their clients' about service promotions, events, training information about IELTS, MYOB, PTE and Accounting and visa renewal reminder, etc.
- The organisation use excel spreadsheet to compute their employee salaries and usually encounters error in computation and takes a lot of time to scan through each record on the document.
- Handling of documents in the company is less secure and unorganised as a result unauthorised access to documents usually happens in the workplace.
2 Vision and goals
The proponents will investigate the most suited students' information systemthat will meet the terms of current issues stated above. This solution will make ZNZ Education modernize and alleviate their business process in terms of giving efficient service to their clients', increase productivity for the company and having clear track of transactions between their clients'.
2.1 Scope
Research and recommend a student information system for ZNZ Education. Review some of the existing student information system implemented by schools and universities that includes SMS (short message service) functions to deliver information to clients', also to review related systems that keep track records of business transactions. The proponents will also recommend a system that will solve their problems with their manual payroll system in ZNZ Education.
2.2 Scope Limitations
This project will not implement a student information system for the subject company. The recommended system may be implemented by the next research team that will design, develop provide training and maintain the technology for the use of ZNZ Education.
3 Project risks and issues
3.1 Risks
- The solution exists will not meet all the requirements of client like their business process
- Converting data into new system is too complicated and also loss of data
- Learning the new system may be upsetting to the company staff
- The recommended system may be cost effective or budget to ZNZ Education
- The company may resists change of their business process
- Implementation, maintenance and conversion of system may require longer time
- Client may not use the system
3.2 Issues
- The project has tight time frame to implement
- The scope of the project is too broad to cover therefore proponents' may not cover all the project deliverables.