VCE Software Development

School-Based Assessment Task

The SAT is project that straddles both U3O2 and U4O1. The marking scheme has been provided by VCAA . This document includes assessment and authentication information, including forms and assessment sheet.

When deciding on what your project might entail, it is important that you read the Programming Requirments documentation provided by VCAA. This lists what is required for your final SAT project. This will change from year to year to ensure student work is kept unique.

Unit 3 SAT: Analyse and document a need or opportunity, generate alternative design ideas, represent the preferred solution design and formulate a project plan for creating the solution

In U3O2 Students must complete the Analysis & Design elements of their Project. There are THREE sections:

1. An analysis that defines the requirements, constraints and scope of a solution in the form of a software requirements specification

2. A folio of two to three alternative design ideas and the detailed design specifications of the preferred design

3. A project plan (Gantt chart) indicating times, resources and tasks.

You will be assessed on the following criteria:

Criteria 1. Understanding of project management concepts and processes

Criteria 2. Skills in using analytical tools to depict relationships between data, users and digital systems

Criteria 3. Interpretation of data to identify and document the software requirements specification

Criteria 4. Skills in generating design ideas and designing preferred solutions

What you will create for U3O2

Criteria 1: You will produce a GANTT CHART. This will be your project plan. You must produce "... a Gantt chart that documents all stages and activities of the problem-solving methodology for both parts of the project. (Student) Prepares a Gantt chart using software that identifies all relevant project management milestones, key dependencies (concepts) and key tasks, sequencing, resources and time allocation (processes). The accuracy, completeness and coherence of the chart contribute to an effective project management plan to monitor progress."*

Criterias 2 & 3: You will produce and SRS including all analysis tools which:

"Identifies a complete and relevant set of data for analysis and uses a wide range of appropriate collection methods and techniques. Uses accurately all features of the selected analytical tools. Depicts accurately all of the relationships between the data, users and digital systems in all analytical tools. Applies all techniques correctly and consistently in all analytical tools." *
"Draws a complete set of conclusions that are connected to, and consistent with, the data represented in the analytical tools. Describes specifically and accurately all the functional and non-functional solution requirements. All constraints and scope are logically connected to the solution requirements Using study-specific language, describes precisely and accurately all relevant aspects of the technical environment and intended audience of the solution. Assembles all the documentation clearly, accurately"*

Criteria 4: You will produce a DESIGN FOLIO which "Specifies a comprehensive set of criteria for evaluating alternative design ideas and the efficiency and effectiveness of the solution. Generates two or three distinctive design ideas that are feasible and original representations of the solution’s functionality and appearance. Selects a preferred design idea for further development based on a complete set of criteria. Expresses accurately and completely preferred design using appropriate methods. Designs are detailed and fully demonstrate consideration*

*http://www.vcaa.vic.edu.au/Documents/vce/computing/SBA_Software_Development.pdf

Criteria 1: GANTT CHART

It is importanat to remember that the role of your Gantt Chart coninutes to play a part beyond the point you hand it in your for assessment. It is possible to create your project in Excel if you do not have a more specific software such as Microsoft Project. It would be best to use a gantt chart or project management software tool as it provides a lot of key features required for the assessment.There are online tools which are good for keeping your project up to date. Try googling "Free Gant Chart software online". Here is one example https://www.canva.com/

The Gantt Chart must include:

all stages of the problem-solving methodology for the entire project
project management milestones,
key dependencies
key tasks,
sequencing,
resources
time allocation

The accuracy, completeness and coherence of the Gantt Chart contribute to an effective project management plan to monitor progress.

You must KEEP your Gantt Chart throughout the project and make adjustments. Keep a journal on your progress with this! It will be vital for U4O1!!

Criteria 2 & 3: SRS

You will create a Software Requirments Spescification document where the analysis tools: IPO, Use Case, DFD, Context Diagram are all included in the appendix. A good place to start is with the Context Diagram - it is the highest level DFD and allows you to identify the enitities and how they interact with the system. Then the Use Case identifies how each of the users will interact with the system. This will isolate each case where that the DFD will expand in more detail. It is important that the DFD is clear and easy to read. It shows the flow of the data through the system. Ensure you follow the rules on pages 42-43 of the Jansen textbook.

Once the diagrams are complete they can be refered to in your SRS document. This document will be LONG! It will need a contents page. ensure you have page numbers. Use references to your diagrams.

This is the SRS structure I recommend:

1. RESEARCH You need to report on your research: What were the data collection methods you used, put yout data collection tools in the appendix. Make reference to them in the text.

2. PROBLEM: Identify the problem the software is required to solve.

3. PURPOSE: Idenify the purpose of the software. Be specific about the input and the output of your solution. Identify it's role within the organisation or how it will be used by the client.

4. USER CHARACTERISTICS: Identify all the user characteristics that will affect the design of the solution. These include: age, expertise, gender, culture, role in organisation, attitudes to change, physical disabilities, education, knowledge of areas realted to the purpose. Identify the main end users, occassional end users and low end users.

5. SCOPE: This will outline all the aspects of the solution that will be included. Outline what possible aspects that will not be included in the final solution.

6. CONSTRAINTS: Identify all the constraining factors that will limit the scope of the solution. These are related to time, access to resources, cost and the skills of users, managers and developers. It is alos importanat to be aware of legal constraints that impact.

7. OPERATING ENVIRONMENT: This is where you need to identify where the solution will be operating - an office, a kitchen, in the street on a portable device. You need to outline all the hardware required for the solution to run including, storage, processors, peripherals and servers. Identify the operating system and any application software required. Think about how the software will operate and describe all the device needed.

8. REQUIRMENTS: You need to list ALL functional requirments and non-functional requirements. Please organise them separtely with ID numbers so they can be refered to again in U4O1.

9. APPENDIX: remember not to include things in your appendix without a reference to them in the body of the report.

Research Tools (Data Collection Tools)
Research Results (Data Collected)
Context Diagram
Use Case Diagram
Data Flow Diagram

Criteria 4: Design Folio

Firstly you need to identify EVALUATION CRITERIA. Here you need to convert each of your numbered requirments from the SRS into evaluation criteria. In the image above I have organised my evaluations criteria into a table identifying each with a ID number (EC01). I have the related functional requirement (FR01). Underneath this is the evaluation criteria written as a question. In the second column are the strategies that would test the criteria. In the third column the criteria is related to effectiveness and efficiency.

The folio requires the student produce 2 - 3 possible solutions. Students need to ensure the create mock-ups and algorithms that are all distinctly different and feasible. You will not get away with creating one dud solution and one feasible solution. They both need to be fully worked out and able to be worked through to completion.

You need to produce a feasible justification for your final design and this must be complete in detail. It is composed of four deliverables"

1. Mock-Ups of Interface fully annotated with object names and functionality

2. Data Dictionary of all variables

3. Object Description Table

4. Algorithm in pseudocode.

U4O1: Apply stages of the problem-solving methodology to create a solution using a programming language that fulfils identified requirements and assess the effectiveness of the project plan in monitoring progress.

In U4O1 Students must complete the Development & evaluation elements of their Project. There are TWO sections:

1. A software solution that meets the software requirements specification and the results of the useability test.

2. An assessment of the extent to which the project plan (Gantt chart) assisted in monitoring project progress in one of the following:

A written report and an annotated visual plan.

You will be assessed on the following criteria:

Criteria 5. Skills in using a programming language to develop a software solution that meets specific needs or opportunities

Criteria 6. Skills in organising and managing data and files.

Criteria 7. Skills and strategies for testing a software solution to meet a specific need or opportunity

Criteria 8. Skills in evaluating the software solution and assessing the effectiveness of the project plan in monitoring progress

What you will create for U4O1

Criterias 5 & 6: You will produce SOFTWARE. Students... "Correctly selects and skillfully applies an extensive range of relevant processing features of the language to develop a correct solution. Coding conforms to all accepted conventions. Writes clearly internal documentation that is comprehensive, contains relevant program comments and is well formatted. Applies efficiently and effectively all relevant data validation techniques to check the reasonableness of input data. Documents the efficient use of a complex algorithm in the solution".

You software must identify " ...a comprehensive, systematic and logical plan for organising files or data to allow efficient and secure access. Organises and manipulates all data through the efficient and effective use of appropriate data structures. Applies a feasible and comprehensive set of procedures and techniques to efficiently and effectively handle and manage the security and accessibility of all files."

Criterias 7 & 8: You will develop a EVALUATION REPORT which "...documents formally and clearly a comprehensive range of relevant test data. Applies suitable techniques to detect all logic errors. Prepares a useability test that comprehensively covers all targeted requirements of the solution. Conducts test using a set of suitable techniques and meets user requirements. Documents in detail a logically classified set of accurate results from the useability test. Implements all necessary modifications to the solution as a result of useability testing."

Your report "proposes a coherent set of feasible strategies for evaluating the efficiency and effectiveness of the solution, if implemented by the user. Strategies align with all criteria. Student evaluation explains in terms of efficiency and effectiveness how specific features of the solution meet all functional and non-functional requirements. Makes reference to a coherent and comprehensive set of criteria. Records correctly and clearly all adjustments to the initial plan during the progress of the entire project. Applies a range of appropriate recording techniques. Explains clearly and coherently the importance of relevant factors that influence the effectiveness of the project plan. Reports clearly and comprehensively the usefulness of the initial plan and its adjustments in monitoring the progress of the entire project."

*http://www.vcaa.vic.edu.au/Documents/vce/computing/SBA_Software_Development.pdf

Criterias 5 & 6: SOFTWARE SOLUTION

This is where you start programming your solution. ensure you follow this document: Software Development Programming Requirements. The document will change from year to year to ensure student work is unique.

Interface

While designing your interface ensure you show peers and your teacher. Ask them if they know what is expected of the user. Don't assume your end user automatically understands what to do.
Use commonly used interface techniques and conventions.

Writing Code

Use naming conventions to make it easy for your teacher to read and follow your variables and identify your objects.
Include clearly written internal documentation. You will thank yourself later in the project and your teacher will thank you also.
Ensure all user input is electronically validated in some way (data type, range check, existance check).
When making decisions about how best to solve your problem in the use of control structues and modularation ask yourself "Is there a more efficient solution?"
Ensure your solution is complex enough to qualify - check this document: Software Development Programming Requirements.
Ensure data security

Data Sources

There are more than one way to store data externally from the program:

Text Files - stores simple lists (1D Arrays). Small files, easy to use.
XML - stores records. It is a sequential file and would require conversion to a spreadsheet or retreival into your software system for the data to be utilised.
Access Databases - stores multiple tables, allows for SQL queries and normalisation.

Criterias 7 & 8: EVALUATION REPORT

This can be a confusing when the evaluation criteria and strategies have already been identified in the Analysis stage. HOn the contrary you can use your evaluation criteria as the foundation for your report. Also, if you have been keeping your Gantt Chart updated as you moved through the project and kept notes on your progress, all you will need to do is format them into your report. Putting the work in throughout the software development stage keeping notes and making changes to the Gantt Chart will make life much easier for you once you get to this stage.

Your EVALUATION REPORT needs to contain:

1. List Test Data and show Expected and Actual results with explanations on changes made to the code

2. Include and desk checking created during the development stage to find logic errors

3. Useability Test includes:

all user requirements
all evaluation criteria
all techniques used for testing criteria (Example: Observed end user enter data to check how easy it was to use")
a list of results from the useability test (Example: User was able to navigate through the software easily")

4. For each evaluation criteria identify feasible strategies for evaluating the efficiency and effectiveness

5. For each functional and non-functional requirement - identify all the features of your software and how they are related to each requirment

6. Present all adjustments to the Gantt Chart

7. Reflect on what made the Gantt Chart effective and suggest it's limitations.

8. Present all recording techniques made during the developments stage: emails, blog, hand written notes etc.

9. Produce a clear conclusion about the usefulness of the initial plan and its adjustments in monitoring the progress of the entire project.