# data[].attributes.body
https://git-scm.com/book/en/v2/Getting-Started-About-Version-Control

https://en.wikipedia.org/wiki/Version_control

# data[].attributes.body
http://en.wikipedia.org/wiki/System_testing

# data[].attributes.body
http://www.nationalarchives.gov.uk/information-management/manage-information/policy-process/digital-continuity/

# data[].attributes.body
https://en.wikipedia.org/wiki/Computer-aided_software_engineering

# data[].attributes.body
https://en.wikipedia.org/wiki/Decision_table

# data[].attributes.body
Physical Diagram of the new system in action.

# data[].attributes.body
System Requirements Resource:

http://philosophe.com/design/requirements/

https://en.wikipedia.org/wiki/Requirements_analysis

# data[].attributes.body
Need to include documentation on manuals which will explain  what the policies are for data recovery solutions and security to consider, the policies on testing, the training requirements, the information and procedures on the system change over. Plus any other documentation that will be provided at the very end of the project e.g. feasibility, maintenance document, training document, requirement specification NOTE don't have produce the documents just explain about the documents are for EXCEPT when in task 5 you do have to produce maintenance recording form and Plan (task to perform)

Other things to consider are;

- Version control considered
- Implementation precautions
- Problems that may arise on implementation (affects to the business)
- Will there be any pilots/prototypes to consider
- Direct change over or running parallel to the old system? Recommendations

# data[].attributes.body
Any diagrams or pictures used please name and ref them and explain what they are and doing.

# data[].attributes.body
- Recommend solutions for customer consideration (Business System Options)
- New development/Bespoke system suggestions
- Upgrade of existing system
- Off-the-shelf solutions
- Comparison of off the self solution and Bespoke (Advantages and Disadvantages)
- Advantages & Disadvantages of solutions given (Business System Options)
- Explain the impact and implications of any changes to customer requirements
- Describe file conversion issues that may arise during systems implementation

- Describe the typical documentation provided on completion of implementation e.g. Operating procedures manual, Security Procedures, Data Recover Procedures, User Guides, Flow Charts, Specification document.
- Test plans, data and policies
- Produce logical design specifications also known as deliverables

# data[].attributes.headline
Task 5 Tip Types of maintenance included

# data[].attributes.subject
Task 5 Tip Types of maintenance included

# data[].attributes.body
Explain the types of Maintenance including documentation.
Corrective Maintenance
Adaptive Maintenance
Perfective Maintenance

# data[].attributes.body
White Box
Black Box
Sand Box

# data[].attributes.body
This includes loads of factors in relation to what will be happening when the system is release e.g. training, upgrades later one, maintenance schedules & reports & forms, support given, documentation like user guides if required, changeover of the new and old system (cut of date of the old system), testing procedures (what testing will you do during the system is up), data recovery procedure.

# data[].attributes.body
This does includes the SDLC lifecycle use and why, but you need to indicate what will be happening at each stage in the lifecycle e.g. the Design, analysis, implementation etc. This can be represented in project management or GANTT charts. In U428 your only mentioning the lifecycle your using and reasoning behind using this lifecycle (justification). Test plans that need to happening during the lifecycle, is some parts of the system going to be signed off when completed during the lifecycle, who involved in that stage of the lifecycle. Do you have a plan B if something does not go right (depending on the lifecycle you use). Can you go back if it goes wrong by one stage (again depends on the lifecycle used and what happens if you can’t?).

# data[].attributes.body
software, licenses, specification on hardware required, file conversions, impact of the new system changes e.g. when Office 2003 was replaced with Office 2007, there was an issue with file conversion. The impacts of the system being integrated to the organistion e.g. training, use of new software or hardware, downtime.

# data[].attributes.body
Similar to feasibility but indicating what the Customer ‘needs’ are. So this should include investigation notes you made with the customer and interrupting their needs including, client’s requirements, any constraints identified and suggestions that might improve the quality or costs of the project.

# data[].attributes.headline
System Requirements to Identify (Task 1)

# data[].attributes.subject
System Requirements to Identify (Task 1)

# data[].attributes.body
- Purpose of what you are doing?
- Background on the business, what is 3AAA (Research website).
- Scope of Project
- User Requirements
- Recommendations of New System (Business System Options*)
- Any existing requirements
- Constraints include - legal, economical, training, platforms*, software, hardware.
- Audience - Stakeholders (Internal & External & Contractors required)
- Political - Data Protection, Copyright issues, licences.
Issues of implementation.
- Questionnaires produced, Interviews conducted (analysed results)
- What's next - Description of Plan of action.