6437 COMPUTER SCIENCE System Analysis and Design

profileltdprinwival
BSAAD.docx

YOU HAVE TO GO FOR CASE STUDY AT THE END OF THIS DOCUMENT

What I have to do is-

01-One class diagram, one use-case and expanded use cases, one BPMN, and one state diagram using Microsoft visio(you can go to lucidchart.com also)

NOTE: included in my marks are the following:

· Feedback given from previous sprints is incorporated in all diagrams

· Assumptions made in each diagram are specifically stated somewhere.

02-Report Requirements (8%):

1. Report Structure and flow (see below for details) (1 Mark).

2. Executive summary, Introduction (0.5 Mark).

3. Final Product Backlog and comments (2 mark).

4. Diagram Sections.

5. Prototyping content (0.5 Mark).

6. A final change report – highlighting all the changes from sprint to sprint (1 Mark).

7. A final burned down report (0.5 Mark).

8. Recommendations/Conclusion (2 Marks).

9. Appendices can include a sample of your CRCs, Screen Shots, and other documentation you see as appropriate that adds value to your proposal (0.5 Mark).

10. Final Report Rubrics

Final Report Rubrics

Criteria

Ratings

Pts

This criterion is linked to a learning outcomeBPMN

BPMN shows main process for proposed system - has incorporated feedback from previous sprints.

1.0 Pts

Full marks

No significant problems with the diagram.

0.75 Pts

Partial marks

Still some minor problems with the BPMN

0.5 Pts

Pass marks

Good effort but still not quite right

1.0 pts

This criterion is linked to a learning outcomeProcess Diagrams

Process Diagrams for other critical processes

1.5 Pts

Performed Exceptionally

All other diagrams make sense and are drawn well, and look consistent with one another.

0.5 Pts

Performed Adequately

Some problems exist with these diagrams.

0.5 Pts

Performed Well

Just some minor problems

0.0 Pts

Performed Inadequately

Diagrams not performed at all well.

1.5 pts

This criterion is linked to a learning outcomeUse-Cases

Use case diagrams and expanded use-cases that were done in previous sprints.

1.5 Pts

Performed Exceptionally

All diagrams and expanded use-cases are done well and have incorporated feedback from previous sprints

1.0 Pts

Performed Well

just still some minor problems.

0.5 Pts

Performed Inadequately

There are still many major problems here.

1.5 pts

This criterion is linked to a learning outcomeClass Diagram

Class diagram is comprehensive and shows the case's full system and incorporates feedback from previous sprints.

1.0 Pts

Performed Exceptionally

This diagrams is well drawn and shows the full system well. Covers most of the main facets of the business.

0.5 Pts

performed adequately

Still major problems here

0.0 Pts

No marks

1.0 pts

This criterion is linked to a learning outcomeState Diagrams

All state diagrams make sense and are consistent and are drawn well and have incorporated previous feedback.

2.0 Pts

Performed Exceptionally

All diagrams make sense and are consistent with one another.

1.5 Pts

Performed Well

Just minor problems and more needed in the descriptions such as transitions.

1.0 Pts

Performed Adequately

There are still major problems but it still looks like they are state diagrams.

0.4 Pts

Performed Inadequately

There are too many major problems. These are not really sttae diagrams

2.0 pts

This criterion is linked to a learning outcomeReport Structure

highlight what you think the main aim of the proposed system is through your product backlog, diagrams (the ones you think are relevant), and the screenshots and explanation of your prototype system. You need to put all your documentation in one document. The report needs to at least follow the standard business report structure . The report flows well and easy to read via the structure.

1.0 to >0.75 Pts

Performed Exceptionally

The flow is there and this is a very professional looking report. This is structured well.

0.75 to >0.5 Pts

Performed Well

Just minor problems with structure but it still reads well.

0.5 to >0 Pts

performed inadequately

The structure has some problems and there are parts that don't read well.

1.0 pts

This criterion is linked to a learning outcomeExecutive Summary and Introduction

Both are distinct and have different purposes and both are well written.

0.5 to >0.0 Pts

Full marks

This will very depending on quality of these sections.

0.0 Pts

No marks

0.5 pts

This criterion is linked to a learning outcomeProduct Backlog

this is a list of requirements that have been ongoing and changing over the sprints. This should be influenced by the stakeholder replys.

2.0 to >1.5 Pts

Performed Exceptionally

Just minor problems or some requirements not considered but nevertheless quite comprehensive.

1.5 to >1.0 Pts

Performed Well

The backlog is good but could be a bit more comprehensive. It may be missing some aspects of the business.

1.0 to >0 Pts

Performed Inadequately

There are some issues with this backlog.

2.0 pts

This criterion is linked to a learning outcomeBurned Down Report

stating 1) what has been done, 2) what needs to be done, and 3) what tasks perhaps have proved difficult.

0.5 to >0.0 Pts

Quality and depth of burned down report.

0.0 Pts

No marks

0.5 pts

This criterion is linked to a learning outcomeRecommendations

should state overall what has been done, and what has yet to be done, and recommendations moving forward, in the context of user requirements. You can include future requirements in this section too

2.0 to >1.5 Pts

Performed Exceptionally

The recommendations make sense and there is an insight into what comes next and what needs to be done next.

1.5 to >1.0 Pts

Performed Well

The recommendation is good but perhaps needs more elaboration on what needs to be done first, and future direction.

1.0 to >0.5 Pts

Performed Adequately

There is not much of recommendations made but more of a summary of the report.

0.5 to >0 Pts

Performed Inadequately

Not real recommendation made and the conclusion or summary is too brief.

2.0 pts

This criterion is linked to a learning outcomeAppendices

Extra material adds value to the report and these appendices are organised and structured well.

0.5 to >0.0 Pts

Appendices add value

Appendices are not just a place to put the rest of the material. They must add value to the report and possibly be referenced by the report.

0.0 Pts

No marks

0.5 pts

Case Study Background

· Due No due date

 

· Points None

AM-UDÖB Incorporated

 Logo.jpg

 

Case Background

AM-Udöb (pronounced Arm-Oodoob) is a technology education enterprise that develops products to teach people (from all ages) programming, robotics, and internet of things.  They see themselves as similar to other organisations, such as Dexter Industries, Raspberry Pi Foundation, and Arduino.

AM-Udöb was created through a conjoint project involving Australian and Swedish programmers and researchers during the period of 2015-2016.  During that year, government initiatives from both countries introduced new education programs to up-skill primary and high school students with computer skills. This provided the two founders of Am-Udöb (Naomi Whiteside and Ulf Melin) motivation in creating new products that would help not just children to learn computer skills but to help anyone who does not have prior IT skills.

In 2016, as a competitor to RaspberryPis, Naomi had the idea to launch their new computer chip as a Kickstarter Project called the UDöb (pronounced Oo-doob) an abbreviation for utforska djupt och brett – meaning explore deep and wide in Swedish – their motto). The product differentiation mainly revolved around being able to be connected to Lego MindStorm robotic sets and have inbuilt components that could link to Microsoft’s Hololens, in order for customer to build their own robots and augmented reality applications. The aim of the product was to not only help people create mini computers at a cheap price like the Raspberry Pi but to go one better and to make robotics and augmented reality easily assessable to everyone.

The vision of both Naomi Whiteside (whose surname was originally Augar, the “A” in AM-Udöb) and Ulf Melin (the “M” in AM- Udöb ) is to allow teachers to create an easy environment for their students to both learn about computing and also to problem solve and create. For the hobby enthusiasts and other consumers, the attraction is a multi-purpose chip designed to empower individuals or small business’s to create their own applications and products.

The UDöb chip has its own built in operating system that can easily interface with other platforms such as OS, Android, Windows, Linux, and Unix. In addition, it has its own visual block programming language, which allows sophisticated programming by joining hexagonal pieces together. It also can be created using mind-maps, jigsaw pieces, or flowcharts. Therefore, it is compatible with visual block languages such as Scratch and BluePrint. The programming tool itself created by Ulf Melin and his team of engineers can act as a stand-alone downloadable programming environment that people can use to create database interfaces (to most Relational Databases and JSON formatted NoSQL databases) and create robotic programming automation tools.

 

Initial User Requirements:

Naomi, being the business brains of the company wants to continue to use the concept of Kick-Starter projects with crowd-funding in order to gauge from the public what new products designs they should create. Hence, Naomi wants an upgrade to their existing website in order to better accommodate crowdfunding. Their initial Kick-Starter project website has a very standard interface, which just has a brief project description and an email link for those who expressed interest in helping or funding the project. Naomi wants more functionality and features, especially those that allow users to keep track of their project ideas, the crowd-sourcing levels for each project, decisions made, and notifications to project owners.

The company is also in need of a system that manages their product inventory, customer purchases, customer profiles, sales reports, and also links directly to their records for crowdfunding. Ulf’s idea is to be able to log in to the website or a phone app to check on the progress of the crowd funding and keep track of how each potential project is funded. He would also like the app to allow customers to come up with their own designs for products or submit their use of their products on the website. For example, a customer had come up with a program created using the Udöb language to link the Hololens, creating a virtual reality textbook using the camera functionality of the Udöb chip. Every year Naomi and Ulf would select the best idea and submit it for crowdfunding, if the product or idea proves popular the customer becomes part of their design team.

Overall, both Naomi and Ulf would like to promote struggling young technically minded people to pursue their creativity and project ideas. Thus, a proportion of profits they make supports project ideas for those who come from underprivileged societies and environments. For the first year of the sale of new products, a percentage of the sales price goes directly towards a fund for supporting the underprivileged.

 

 

Addition Information

The following are people connected with AM-Udöb, which you can try and contact for clarification of requirements or obtain new information (their email addresses are included). The following summarised information is what you have initially gathered from viewing public and internal documents.

The Australia Guild

Naomi Whiteside (Executive Director Australia - EDA):

Contact:  [email protected]

Naomi Whiteside is very passionate about the marginalised groups in society because of her own humble beginnings. Getting products out to the community at no cost or at least at low cost for people to learn about computing and the Internet of Things has been her goal for the last 3 years.

Her goals for the proposed system are:

· The system needs to support her company in creating low cost products enabling people/schools to have access to new technology. Her current focus is on virtual and augmented reality tools.

· The current website needs to be a catalyst for building a safe community environment where inventors and users share ideas.

· Although she still wants to turn around a profit and sales does matter to her, she has been keen to give out loyalty discounts to returning customers.

 

Yee Ling (Database and Accounts Manager - DAM):

Contact:  [email protected]

Yee Ling used to work for PWC (Price Waterhouse and Coopers) as a senior auditor and has recently been appointed to look after the accounting side of the business. This includes being the local database administrator. She is profit oriented and is concerned about budget overruns for new projects. She is currently concerned that there is no credit check within the current revenue process. Her motto is “let’s be charitable only if we can afford it”. She believes that a customer’s credit needs to be validated first before a new customer can order a product.

 

 

Vince Bruno (Principal Hardware Engineering Manager - PHEM):

Contact:  [email protected]

Vince was part of Ulf’s engineering group that designed the actual UDöb chip. He is currently based in Australia and through online collaboration with the Swedish team has continued to develop the UDöb chip. Vince and his team of engineers have embarked on evaluating and selecting the best user ideas.  If there was to be a new information system he would like it to support his team to bring the best user ideas to life, as real products and as product packages ready for sale.

 

Ian Storey (Principal Sofware Engineer - PSE):

Contact:  [email protected]

Has only recently come onboard and is enthusiastic of the new tools as he spends a lot of time at local high schools promoting the fun of coding and robotics. He believes in a cashless society and thus, believes having an app is top priority for his company to allow all transactions to be done online. However, most of his time has been enhancing their programming tool and increasing the tool’s libraries, and thus has no time himself to develop this app. He also believes that everything should be open-source and thus, has just put forward his proposal to Fredrik and Ulf from the Swedish guild to make the UDöb source code open-source. He believes a website should allow the sharing of ideas and code from people using the UDöb programming tool to build applications.

 

Paul Mercieca (Communications and Information Manager - CIM)

Contact:  [email protected]

Paul’s main focus is to gather and manage information about the profiles of their customers and purchasing trends thus, he is keen to see the new system support his information management needs. He is often the data analyst for both Naomi and Ulf’s strategic plans. Paul is a librarian by trade and has a background in business analytics, and at the moment does not believe he has any effective tools to analyse the information gathered concerning the business. He also does a lot of promotion work for the company as a side role and is often abroad. He sometimes acts as a liaison among the Swedish, South East Asian, and Australian Guilds.

Konrad Peszynski (Events Manager - EM)

Contact:  [email protected]

Konrad joined the Australian guild recently and his job is to create awareness for the company’s products and expertise. Over the past year he has organized product expos called “Raids” in Melbourne, Sydney, Perth, Linkoping, Gothenburg, and Stockholm. Each “Raid” consists of workshops, product stands, keynote speakers, and seminars. Competitions are also held at these “Raids”, such as the Robot territory Wars (RTWs) where teams around the world bring their group of robots to battle for territory within a battleground set (a world created by AM-Udöb engineers). Konrad’s main concern is that the more traditional methods of tv advertisements, magazine posts, flyers are costly and have limited reach. He would like the new website or app to communicate his events, and to have a stronger social-media presence.

 

Ian Searle (Project Manager - PM)

Contact:  [email protected]

Ian’s primary task is to ensure projects are continued within cost and time budgets. He has monthly skype meetings with both Naomi and Ulf to report on progress of all of AM-Udöb’s projects. He has a team of Scrum leaders that report to him weekly. Thus, he would like the system to be able help generate project progress reports when he needs to discuss things with the executive directors. In addition, he would like the new system to consider security issues and to filter out initial project ideas before they get to selection by Vince and his team.

 

Arthur Adamopoulos (Quality Control Manager - QCM)

Contact:  [email protected]

Arthur leads a team of “Pillagers”. A “Pillager” is an engineer that takes hold of a product – hardware or software and rigorously pulls it apart and tests it under the company’s own comprehensive testing scheme. Apart from the normal tests run on hardware and software, AM-Udöb’s chips were also created to withstand some physical pressures. Therefore, for hardware products testing also includes physical testing for durability, water-resistance, fire-resistance, etc. Software testing includes hacking thresholds and code-flexibility (ability to link to other visual programming tools).  Often Arthur’s job is to troubleshoot new designs and also recommend alterations to products. A product is only approved for release once it has gone through Arthur’s “Pillaging” process and gained his seal of approval.

 

Pradip Sarkar (Quality Control Liaison - QCL)

Contact:  [email protected]

Pradip is part of Arthur’s team of “Pillagers” but is often used as a co-developer, a type of liaison among the design, development, and testing teams. He often visits the Swedish Guild to direct test products and to give recommendations to Ulf’s team. Thus, he is a hard person to get hold of as he is often overseas. He has recently taken on a new role for Ulf to locate new ideas and new talent for their development team. He is currently in India.

 

 

Swedish Guild

Ulf Melin (Executive Director Sweden - EDS)

Contact:  [email protected]

Ulf actually started the company with Naomi when they met at a technology forum in Europe. He is considered as the “Steve Wozniak” of the company and often leaves the management duties to Naomi. He is also a committed philanthropist.  Although he prefers to stay at home and tinker with things, he realised a long time ago that he can’t do things alone. Therefore, it was when he was leading a small team of engineers that his ideas for the UDöb chip and the programming software tool was fully realised. His ultimate vision is to create an online community where struggling and underprivileged developers can come together in cyberspace to collaborate on projects. Thus, he would like to see the system facilitate and support this functionality, and have this evident on their website and app.

 

Fredrik Söderström (Principal Hardware Engineering Manager - PHEM )

Contact:  [email protected]

Fredrik is the lead engineer for Ulf’s engineering team. These days his main focus has been to review and contribute to the continuous redesign of the chip. In addition, as the Swedish Guild is a smaller team, he often helps Konrad with promotions and event organising, specifically on his side of the world.

 

Jonathan Cruz (Subject Matter Expert - SME)

Contact:  [email protected]

Jonathan was involved in the developing of the UDöb programming language. His main contribution was to create a language compatibility tool for the programming language, allowing many people around the world to program in their own language. Being a Subject Matter Expert, his role extends to promoting their products at “Raids”.

 

South East Asia Guild

Huan Vo-Tran (Subject Matter Expert South East Asia - SMESEA):

Contact:  [email protected]

Huan used to be part of Ulf’s development team that designed the new software tool that enables even primary school kids to perform sophisticated programming of the UDöb chip. He considers himself a tech-junkie and coming from the poorer areas of Vietnam really appreciated the opportunity given to him by Naomi and Ulf to explore his creative and technical talents. He has recently been promoted to lead the promotion side of the company for South East Asia, and directly reports to Naomi. At the beginning of this year, Huan moved back to Vietnam to be with his family. Skype and online tools has enabled him to do his job effectively. His main job now is to promote the company’s products for the South East Asia Guild, as a Subject Matter Expert. Naomi found that there is a new effective practice used in new businesses, the use of Subject Matter Experts. Using subject matter experts to sell products to consumers, as consumers are more comfortable talking to people who know the product inside and out rather than just from a mere sales person. Since Huan has been part of Ulf’s development team in the past, he has in-depth knowledge of how the products operate, both hardware and software. Contacting him through email is simple as his local email is linked to his Australian email address.