7 USER DOCUMENTATION
Contents
7.1 Minimum System Requirements
7.2 To Operate the Program
7.3 Main Menu
7.5 To Enter the Subscriptions Menu
7.6 To Enter the Events Menu
7.6 Backing up the System
8 APPENDICES
Appendix 1
Appendix 2
Appendix 3
Appendix 4
Appendix 5
Appendix 6
Appendix 7
Appendix 8
Appendix 9
Appendix 10
Appendix 11
Appendix 12
Appendix 13
Appendix 14
9 BIBLIOGRAPHY
1 Analysis
1.1 Statement of the Problem
The Current System
Investigation of the current system was made through an ………
Questions were prepared before the interview and a transcript of the interview is shown below.
1.3 Interview
How does the Current system work?
When are subscriptions paid?
What happens if a member misses a payment?
What happens to the money that is collected each month?
What documents are involved in the current system?
What volume if data is involved in the current system (e.g. how many group members?)
Do you have any specific requirements for the new system?
What Hardware and Software do you have available for the new system?
Is any of this data confidential?
Are records ever removed from the system to be archived?
How is the information held about each member?
Does information need to be held about each leader?
Do you have any backup facilities?
When does the financial year end?
1.4 Summary of Interview
i.
ii.
1.5 Problems with the Current System
The current system is ….
1.6 Requirements of the new system
General Objectives
Specific aims
Specific Objectives
The system must perform the following functions:
1.7 Constraints and Limitations
- Expertise
- Qualitative
- Quantitave
It is proposed to implement the new system by the end of the financial year, March 31st which would be a convenient change over time from the present system to the new (see Time Plan, Section 3).
1.8 Recommendations
I propose to implement a new computerised system to replace the existing manual system. etc
1.9 Summary - Data Flow Diagram of the Current System
2 Design
2.1 Consideration of possible solutions
Using A Programming language
Name a programming language
Advantages:
Disadvantages:
2.2 Using a Database Package
Advantages:
Disadvantages:
2.3 Proposed Solution
Input Design
- Sketches and diagrams of forms,etc. Any inputs into the system that will become an electronic document
Menu Design
- The main menu will contain the name of the organisation –
-
Each menu will have an individual heading which uniquely identifies it, for example ‘Main Menu’, ‘Subscriptions Menu’ and so on.
-
Where a menu leads to a sub menu, the heading of the sub menu will show the choice that was made on the previous menu so that the user will always have a clear idea of what option is currently operative. For example if the user selects ‘Members Menu’ from the main menu, the sub menu will be headed ‘Members menu’
- All options on each menu will be activated by a button, which will take the user to whatever option that accompanies the button.
- A standard colour scheme will be applied throughout the system with uniform text and background colours. Colours are selected for clarity and ease of viewing.
Sample screen layouts must be shown in the User Documentation.
A chart showing the relationships between menus is shown on page xx.
2.6 Security
Describe any password system being used. Cross reference it to the User Documentation.
2.8 Output
List the different types of report required from the system.
2.9 Output Design
Draw a design. An example is shown below:-
Please refer to User Documentation Figure x to view implemented menu hierarchy based on the above design.
Logon Screen
Main Menu
Example of other Menus
Example of Invoice Design
2.13 Design of Input Form
2.16 Security
A password will be attached ….
2.17 Testing
- Testing will be carried out
3 Time Plan
3.1 Time Plan
From the project start to completion, a total of 26 weeks was estimated. Realistically, 4 weeks was built in to allow for holiday, sickness etc. Below is a chart listing progress.
4 Implementation
Facilities Offered by Microsoft Excel
Describe facilities in Excel with screen grabs
5 Testing
5.1 Test Plan
5.2 Test Results
Test 1: Test password entry into system
The correct password has been entered therefore the Proceed button is enabled.
An incorrect password has been entered, therefore the Proceed button stays disabled.
Test 2: Test Main Menu options
All Sub-Menus open correctly. Please see screen shots in User Documentation Figure 5.
Test 3:
etc
Evaluation
Evaluation
The system has been completed and installed on the …… computer.
With reference to the Objectives listed in the Analysis section, 1.6, page 8:-
6.2 Comments on the Implemented System
This section is a combination of the feedback from the end user and what I discovered: -
6.3 Expanding the system
All of the above will be implemented in ICT6.
7 User Documentation
Contents
7.1 Minimum System Requirements
- IBM compatible PC with preferably Pentium 400Mhz processor, 5GB hard disk drive
32 MB RAM and SVGA monitor display
- Hewlett Packard 5L laser printer or later, or Hewlett Packard/Epson type Inkjet printer with 600dpi minimum.
- Microsoft Windows 98 operating system
- Microsoft Access for Windows version 7.00
- Microsoft Word 97
7.2 To Operate the Program
- To start the program, click on the Excel icon on the desktop as shown in Figure 1.
- Once the spreadsheet name has been clicked the program will be activated and a logon screen will appear as shown in Figure 3.
- Once you have entered the password you must then enable the ‘Proceed’ button by pressing enter on the keyboard.
- Once the button is enabled (the Proceed text turns to black) click on the ‘Proceed’ button to open the Main Menu.
7.3 Main Menu
- The Main Menu screen will appear as shown in Figure 4. (This is just an example)
-
Figure 5 shows the menu structure of the program (This is just an example)
8 Appendices
Note:
VBA Code shown in bold in Appendices 6-14 was created by the candidate
9 Bibliography
– Fundamentals of Design
