Question 1
Narrative:
The examiner of the course offering must set up the assignment before markers can begin marking using the software. He or she needs to create an assignment to be marked, and input each assignment submission. The examiner will select markers for the assignment, and specify how many assignment submissions each marker will mark. The examiner will then use the software to allocate assignment submissions to each marker.
Human roles, computing systems, or concepts referred to in the narrative are not explained. For example, the software developers who are one of the target audiences of these specification may not have studied at this university, and may not understand terms like "course", "subject", "semester" or "examiner".
You must provide a glossary that explains any such term that will be mentioned in your specifications that might not be clear. Again, you may have to be creative whenever something is unclear, but the terms mentioned above should already be known to you. In your definition, as well as explaining the concept, you should list what properties or attributes define or uniquely identify such an entity as well as other important attributes. This will help you to know how the system will work and what needs to be entered. For example, given an assignment, what else is needed to define an assignment submission.
Your specifications should be more physical than the narrative. For example, just how does the examiner input the assignment submissions? Clearly the examiner is not entering the student's work, but is telling the system about each assignment to be marked. What exactly must be entered? How does he enter it? Does he create a text file, and upload it? Does the software present the examiner with a form with tick boxes associated with each student, and the examiner ticks the appropriate one? There are plenty of other possibilities. You may find that you need to add things to the glossary that were not mentioned in the narrative.
Your answer must take the form of a numbered (numbered using a letter) goals, which you must identify from the narrative, followed by a glossary, followed by numbered requirement specifications. The requirement specifications should reference the goals.
Question 2
Class Diagram
Draw a UML class diagram that models the aspects of job agencies that are described below:-
• Some of the employees of the agency, are agents.
• Each agent has domain knowledge in only some classes of positions. For example, an agent may specialise in software developers for the banking industry. Some classes of position have more than one agent that has domain knowledge in that field. Not all agencies have expertise in all fields. For example, an agency that specialises in secretarial positions may not deal with builder's laborers, and it may not have any agents that have domain knowledge in that area.
• Agencies typically keep the details of the employers they have dealt with, even when they have no current business with them.
• Agencies are approached by employers seeking employees.
• One of the agents will be nominated as the first port of call for a given employer.
• Employers will provide the details of positions to an agency or possibly to several agencies.
• The details of each position, including contract details are recorded, and one of the agents with domain knowledge in corresponding class of positions will be made responsible for that position.
• Your model must show:-
o Named classes
o Named associations and association multiplicity
o Example attributes of classes (at least 3 attributes, but as many as possible)
• Do it first using pencil and paper, then use a UML tool to create this diagram. Try googling "Roses are rational. Violets are GNU.".
Question 3
Statechart Diagram
Design a floating point calculator.
As a starting point, you have been provided with a calculator that is only capable of entering integers. The design consists of a statechart, a description of the data and some pseudocode that describes the methods invoked or referred to by the statechart. You should verify that the design works as expected.