You are asked to write up a comprehensive "log” of all activities undertaken until Week 19. You should not simply aggregate - rather, you need to add your own critique, analysis, extra-added value to any work undertaken in practical classes. Credit will be given for this added-value as well as for comprehensiveness. A high standard of written English expression is needed as is clarity.
It is not required to talk about every week, rather give an overview of what you have done so far on the unit, with evidence that covers all of the topics you have worked on. It is important that the work log is about what you have done, not what your group has done. All descriptions, comments and reflection should be written by you about work you personally were involved in. It is ok to use examples of your groups work only if you write your own description/comments about what your contribution to the work was.
Typically, you should think of the maximum length as 10 pages. (You may put additional examples/diagrams in the appendices)
SOME EXERCISES UNDERTAKING DURING PRACTICALS
Practical Week 2 - KIOSK CASE STUDY
Form into small groups - these can be ad hoc groups for now not the final agreed groups:
1 Write down a numbered list of functional and non-functional requirements for the KIOSK system. Make sure each requirement is numbered, [2.1, 2.1.1,3,3.1 etc.]with a date and a source: client brief, team, user etc.
2 You need to design a simple questionnaire to be used to interview "real" potential users of the system. It would be best if you can also mock up one or two "EXAMPLE" e.g. Powerpoint/ XHTML etc low fidelity paper prototypes to show real potential users to help them "visualise" what the final system will look like. Agree a plan of action - who will you approach so as to gather a realistic set of reqs.?
3 Explore the practical tools available in the laboratories to support requirements definition.
4. Obviously the initial task is for the TEAM to source requirements but later these will be refined by inputs from others.
5. It would be good also to undertake a simple market survey of existing KIOSK information systems so you can benchmark your system against others of a comparable nature.
6. The core of the system will be Oracle but other tools can be used as well….
WRITE UP EVERYTHING YOU DO IN PRACTICAL SESSIONS INTO YOUR OWN PRACTICAL LAB BOOK - this will be assessed at the end of the unit. You also need to add your own "added-value" to any work undertaken in class by a group.
Functional /non functional
Practical week 3 and 4- Soft System Methodologies
Consider the following ROOT DEFINITION:
A university owned and operated system to award degrees and diplomas to suitably qualified candidates (X), by means of suitable assessment (Y), (in conformance with national standards), in order to demonstrate the capabilities of candidates to potential employers (Z).
1. Prepare a Rich Picture which shows structure, process, conflicts and the environment.
2. Identify the CATWOE.
3. Identify the measures of performance for the Effectiveness, Efficacy, Efficiency
4. Finally, construct a conceptual model
Then, start working out the Root Definition for the Kiosk system and follow the above steps for your assignment.
Week 5 - ERM
Your task is to create a conceptual ERM for a database to store details of Projects for a company.
- The client has requested that you do not add any additional codes/id numbers. Only use the data they have provided.
- You should be as efficient as possible, so only store data that you cannot calculate otherwise
- Each Cost Centre runs multiple projects
- All managers are employees of the company
- All hourly rates vary from project to project
- Below is a complete Project Management Report form
Week 7 - Recycling Machine
The system can recycle returnable bottles, cans and crates. The machine can be used by several customers at the same time and each customer can return all three types of item on the same occasion. The system has to check, for each item, what type has been returned. The system will register how many items each customer returns and when the customer asks for a receipt, the system will print out what was deposited, the value of the returned items and the total return sum that will be paid to the customer.
An operator also uses the system. He asks for a printout of the total number of items that have been deposited at the end of each day. He has right to change the deposit values of the items through a console. When anything goes wrong with the machine, the operator will be called by a special alarm signal.
1. Create a Use Case Diagram for the above system
2. Remember to go through all of the steps, and to look for places where include/extend or generalise can improve your model.
3. Create Scenarios for each of the Use Cases identified
Remember to think about alternative paths through the Function.
4. Turn those scenarios into Activity Diagrams (one for each Use Case)
Remember: This is not an exercise in learning to use Visual Paradigm. This is an exercise in you thinking about system modelling! You can do all of this on paper, but Visual Paradigm is a useful tool that will increase your productivity
Below is a link to the user guide for Visual Paradigm:
In particular the guide to creating diagrams will be useful:
Week 12- Normalisation Exercise A
Look at the project management form and create a 3NF set of table for it
The client has requested that you do not add any additional codes/id numbers. Only use the data they have provided.
You should be as efficient as possible, so only store data that you cannot calculate otherwise
Each Cost Centre runs multiple projects
All managers are employees of the company
All hourly rates vary from project to project
Below is a complete Project Management Report form
A-Range An excellent detailed but concise Worklog, presenting a very well structured summary of personal learning experience, clearly mapped to the course learning outcomes. The content is clear and comprehensive, with well defined tasks at suitable levels of abstraction demonstrating a high level of understanding of the task as a whole, and also including all pre-specified details. The reflection on the task demonstrates advanced critical appraisal and reflection and is suitably referenced.
B-Range A well detailed and concise Worklog, presenting a well-structured summary of personal
learning experience, clearly mapped to the course learning outcomes. The content is clear and well detailed, with clearly defined tasks at appropriate levels of abstraction, including the majority pre-specified details. The reflection on the task demonstrates critical appraisal and reflection and is well referenced.
C-Range A detailed and reasonably concise Worklog, presenting a structured summary of personal
learning experience, mapped to the course learning outcomes. The content is appropriately detailed, with defined tasks at reasonable levels of abstraction, including pre-specified details. The reflection on the task demonstrates appraisal and some reflection.
D-Range A suitable Worklog, presenting a summary of personal learning experience, with some link to the course learning outcomes. The content is has some details with defined tasks, including some
pre-specified details. The reflection on the task demonstrates appraisal of the task.
E-Grade A Worklog, presenting very little detail about the learning experience, but lacking in structure and mapping to learning outcomes. The content is has little details or defined tasks, and little or
none of the pre-specified details. The reflection on the task lacks critical appraisal of the task
F-Grade Presenting almost no details about the learning experience, little or no structure and no
mapping to learning outcomes. The content is has little or no details or defined tasks, and little or
none of the pre-specified details. The reflection on the task lacks any critical reflection or