ISYS1051 Digital Business Design
ISYS1051 Digital Business Design and Innovation
Assignment 3: Prototype (20%)
Your team is required to produce a prototype for a business innovation that has a technology component. This must be produced as a Word file shared in One Drive (or a Google doc shared in Google Drive) with each group member using a different colour to indicate their contribution. There must be a colour chart at the start/or appendix of the report showing which colour each member has used. Also, please provide a chart showing the assignment of the tasks to each member (where possible, to minimise any conflict). Marking will be done for every team member individually if equal contribution is not observed. Your team may choose to allocate each section to a member or arrange the workload equitably in some other fashion. One person from each group will upload a pdf version of the report in Canvas.
The team will then present the special features of the prototype to the class as if they were doing so to the owner of the business. Marking will be done for every team member individually. This component is assessed separately, as the presentation (worth of 10%, done in week 13).
Although the nature of the proposed new system will determine some aspects of the prototype, the following are expected sections:
- Executive summary and referencing (1 mark)
- Business case (Clear indication of issues of the current system, benefits and costs of the new system) (2 marks)
- Architecture design (network, hardware and software infrastructure needed) (5 marks)
- User interfaces (forms, screens, dialogs, webpages) (5 marks)
- Implementation plans (changeover process) (2 marks)
- Documentation and operation manual (2 marks)
- Change management plans (2 marks)
Note. The prototype will be marked on the basis of how realistic each section is for the business and the extent to which the prototype could contribute to the business. Extra credit will be applied for originality and creative use of technology.
Structure of the report:
Executive summary (1 mark): By now, you should know these two important things.
Business case (2 marks): This section is the summary of your report 1 and 2. Briefly, discuss the issue(s)/problem(s) of the client’s business, briefly discuss the solution(s) (which is necessarily a technological innovation). Here, you may use diagram/s (e.g., BPMN, Fishbone, Overall Use Case) to focus your problem/solution. Next, summarise the costs, benefits, and project details (e.g., time, quality/scope, budget). Remember, we do not appreciate a copy and paste of the previous reports; rather, this should be a brief discussion (which will relate the next sections).
Architecture design (5 marks): Here, you should explain the architecture of the proposed system. You may use client-server architecture. Within client-server architecture, you can apply different servers (depending on the solution you are suggesting), may also discuss about thin/fat clients and rationality (do not provide any theoretical stuff such as what are they etc.). Also, you may discuss about Internet-based architecture such as cloud computing. In that case, you need to discuss how it will work, the provider, (consider the costs in cost analysis), and what will be provided in terms of securing data. Finally, you may discuss the networking topology. You should look at lecture 9.
This may be the physical architecture and/or the systems architecture. Physical architecture may consist: what technology is required, what space will it need, what wires will need to be placed,… etc. Alternatively, the systems architecture will probably discuss: what software is needed and how are the various components of software connected, is there a database or other data store, is there data needed external to the system and if so what part of the system captures it, … You can make the material as technical as you like.
Presentation: When you present this section, you will need to make clear to the manager that you have designed the prototype, but there are physical and perhaps software components yet to be purchased. You should leave the manager with a clear idea that there are different parts to the system, not just what can be seen.
User interfaces (5 marks): These may be made in any of the three ways (Visual Basic interface, MS Access interface, Website/webpage) you have been shown (or any other you know about). They (it is okay if the buttons, for example, are not functioning) do not have to work but you should have a clear idea of all the ones that will be needed.
Presentation: When you present this section, you should do it using a major use case (usually the one where the business makes money). In this section, you should present some (most important) screenshots of the interface. You should show some other interfaces and leave the manager thinking you have covered all the use cases and knowing the design features (how the screens are arranged and perhaps how data validation has been done).
Implementation plans (changeover process) (2 marks): You need to have detailed plans of what is needed to implement your system (install wires, computers and the desks they go on, throw out old system components you have replaced, hire new people, …). Next, among the four alternative methods of system conversion, discuss the conversion method you suggested for this client/solution, and discuss why it is suggested.
Documentation and operational manual(s) (2 marks): A new employee needs a manual; old employees will then need reminder material such as a poster of card near the transaction terminals. When you present this section, you should give some examples of the differences between the materials for different purposes. You may show examples of online or paper-based materials demonstrating that the language you have used is appropriate to your intended trainee.
Remember, you are not writing the manuals but point out what will be provided to the client once the project is delivered. Will the manual be available on-line or just paper-based? If the first one, who will host it, update it, maintain it? All nitty gritty is welcomed. You should look at lecture 10.
Change management plans (2 marks): You need to manage the change process. First identify the various people who need to be trained and what their training needs are. Then, decide when the staff need training and can be removed for training; convince the staff that the new system is a good idea and so on. You may read lecture 10 well in advance and make sure you have the sections of a change management plan as your paragraph headings for you plan.
Presentation: When you present this section do not go into detail on the contents of the material as the manager is not at that level. The points you make are that everything that is needed to extend and adjust the system is in your package and that the design has been made deliberately extensible in some way (a new office can be opened, new products can be added, new terminals can be added, …).
Professional look and referencing (1 mark)