Information Processes and Technology

Home > Information Processes and Technology > Project Management & Project Work > Expectations of project work

Expectations of project work

Project work in the HSC is intended to give students an opportunity to plan, design and implement an information system that has a purpose.

The chosen information system should be:

For further information on project work see:

Outcomes

This material addresses aspects of the following syllabus outcomes:

A student:

H1.1 applies and explains an understanding of the nature and function of information technologies to a specific practical situation
H2.1 analyses and describes a system in terms of the information processes involved
H2.2 develops and explains solutions for an identified need which address all of the information processes
H3.2 demonstrates and explains ethical practice in the use of information systems, technologies and processes
H6.2 selects, justifies and applies a methodical approach to planning, designing or implementing a solution.

Source: Board of studies NSW, Stage 6 Information Processes and Technology, Preliminary and HSC Courses (2007)

Go To Top

Ideas for projects

Find a problem that needs to be solved in your school. Such problems could be:

Always keep in mind the social and ethical issues and identify these as you progress through the project. These issues may influence the end result of the project and thus, reduce its impact on the information system. Remember also to document everything you do so that you can thoroughly explain your solution to the problem. The other key is to communicate to others and be a good listener, this will also help solve the problem.

In order to achieve any of these projects you would need to follow through the steps as follows:

  1. Understanding the problem

    Each of these problems will have different goals, it is up to you to develop a clear understanding of what the problem is. Create a prototype for the problem you have chosen. For each of the problems above, the prototype could be items such as a storyboard, an algorithm and a filing system. Once the problem has been understood then you can look at:

  2. Planning

    Once you have that understanding for the problem, you can look at seeing the problem or possible solution from the viewpoint of others within the organisation. A feasibility study would need to be considered. A feasibility study is a method of looking at the problem and identifying if it is possible. Such items as surveys, interviews and any documentation that is available could be used to make the necessary judgements. Consideration also needs to be given to the areas of finance, technical requirement time and the information system at hand. You also need to look at where the participants fit into the system.

    You will also need to determine a schedule (a time limit) for getting the problem solved. If the problem is happening within a few weeks but it would take you many months to find a solution, it may not be worth solving. You need to identify a set of sub-projects that are part of the main project, because they directly influence the problem. You also need to identify the participants, the information technology needed and the data or information required.

    After you have completed the feasibility study, you need to come up with an appropriate solution based on the results you obtained.

  3. Designing

    The prototypes you created now need to be refined and modified to solve the problem. At all times consider where the participants are to be involved in the information system. You will have to identify the tools needed to solve the problem and acquire the resources necessary to assist with the solution. At this point, you should be using a variety of tools to help design the solution:
    • Draw dataflow diagrams to show the flow of data through the prototype.
    • Draw context diagrams to identify graphically the system you are proposing as a solution. Use the prototype as the system.
    • Identify the order which the prototype's data or functions are to be organised. Use either a decision tree or table to achieve this.
    • Create a data dictionary to identify the inputs to the prototype and therefore identify the data required for the system.
    • Create a storyboard to describe all screen elements and their placement and indicate links between these elements.

  4. Implementing

    At this point, you need to consider:
    • What training will be required to achieve a solution i.e. with the laptops problem, maybe staff or some students don't know how to manage using them or have never used one. What would be the consequences of implementing without training?
    • What conversion method would you use to implement and why? Is Phasing in better than direct? Would pilot be helpful or would parallel be a better way to get things going?
    • What methods will you use to test the system? What data are required to input into the system? What are you expecting as output? What makes the results of the data valid for your problem? Does it help solve the problem or does it cause more questions to occur?
    • Once you have selected a conversion method, explain how you would implement this in the system. Does any conversion method suit a problem
    • Documentation is now required. Write a operation manual that explains the operation of the solution that solves the problem. Producing an operation manual will instruct users in the use of the system?

  5. Testing, evaluating and maintaining

    Now it is time to use the data in the system. What happens? Does it help give a solution? Or does it cause more problems?

    Does the data now match the original criteria you came up with during feasibility?

    Can the problem be solved?

    Trial and use the operation manual. Are the instructions clear? Is the operation manual user friendly?
Go To Top
Neals logo | Copyright | Disclaimer | Contact Us | Help