University Project: System Design and Mobile App for Picoso

This report presents a case study on Picoso and the implementation of a mobile application for its business operations. It encompasses three key areas: a comparison of the advantages of mobile applications versus web-based systems, a Work Breakdown Structure (WBS) for the front-end development of the mobile application, and a set of recommendations for Picoso to successfully implement the system. The report highlights the benefits of mobile applications, such as faster processes, personalized content, instant online/offline access, and add-on features. The WBS outlines the project's phases, tasks, durations, and dependencies, providing a structured approach to development. Recommendations include using the Prince2 methodology, utilizing advanced technological tools, integrating secured payment options, and designing a user-friendly, personalized interface. The report concludes that mobile applications offer significant advantages over web-based systems and provides a practical framework for Picoso's mobile application project.

INTRODUCTION TO SYSTEM DESIGN
Introduction to System Design
Name of the Student:
Student ID:
Name of the University:
Author’s note:
<<Name of the Student>> Page 1

INTRODUCTION TO SYSTEM DESIGN
Executive Summary
The following report had been made for the case study of Picoso and the use of mobile application for
performing their business operations. The report consisted of three topics and they were comparison
of the benefits of mobile application and web based system, WBS for the project of implementing
mobile application, and some recommendations to Picoso for implementing the mobile application
system.
<<Name of the Student>> Page 2

INTRODUCTION TO SYSTEM DESIGN
Table of Contents
Introduction............................................................................................................................................. 1
Topic 1: Comparative Benefit of Mobile Application over Web Based System........................................1
Topic 2: Work Breakdown Structure for Front End Development............................................................2
Topic 3: Recommendations to Picoso...................................................................................................... 5
Conclusion................................................................................................................................................ 6
Bibliography............................................................................................................................................. 7
<<Name of the Student>> Page 3

INTRODUCTION TO SYSTEM DESIGN
Introduction
Mobile applications have changed the prospect of performing business and reaching over to
the global customers (Bharadwaj et al. 2013). The mobile application technology have been
implemented for forming the support and development to the various organizations for developing
effective marketing plan, and managing the sales process by integrating the customer’s data with the
stock inventory system.
The following report has been made for the case study of Picoso and the use of mobile
application for performing their business operations. The report consists of three topics and they are
comparison of the benefits of mobile application and web based system, WBS for the project of
implementing mobile application, and some recommendations to Picoso.
Topic 1: Comparative Benefit of Mobile Application over Web Based System
The comparative benefits of mobile application over web based system are faster processes,
personalized content, instant online/offline access, and add-on features (McWherter and Gowell
2012). These have been explained below,
Faster Processes: The mobile applications would be implied for the development of the specific
processes and the customer eccentric development (Kim et al. 2013). The mobile application would
increase the proficiency of the faster processes for the organization and customers.
Personalized Content: The mobile applications provide user’s choice contents and it would be helpful
in forming the specific content listing for the users (Saarijarvi et al. 2014). The personalized content of
the customers would be helpful for easing the user experience and satisfaction.
Instant Online/Offline Access: The mobile applications have some offline actions that would be
helpful for the customers to use the application even in offline mode (Schmit and Dustdar 2015). The
offline access is very helpful for the customers as sometimes there is absence of internet connection
and they can use the mobile application at those times too.
Add-on Features: The add-on feature of mobile application makes it more usable for the customers
and organization. The NFC connection, bar code scanner, and QR scanner are also helpful for the ease
of the transactions of the business organizations.
Topic 2: Work Breakdown Structure for Front End Development
WBS Task Name Duration Start Finish Predecessors
0 Development of Mobile Sales Application for
Picoso 91 days Mon
1/1/18 Mon 5/7/18
1 Project Initial Phase 14 days Mon
1/1/18
Thu
1/18/18
<<Name of the Student>> Page 4

INTRODUCTION TO SYSTEM DESIGN
1.1 Portfolio Strategy is developed 2 days Mon 1/1/18 Tue 1/2/18
1.2 Product Strategy is developed 3 days Wed 1/3/18 Fri 1/5/18 2
1.3 Project Team is formed 4 days Mon 1/8/18 Thu
1/11/18 3
1.4 Structure of the organization is formed 2 days Fri 1/12/18 Mon
1/15/18 4
1.5 Roles are assigned to the team members 2 days Tue 1/16/18 Wed
1/17/18 5
1.6 Norms are developed 1 day Thu
1/18/18
Thu
1/18/18 6
2 Documentation and Resource Accumulation
Phase 22 days Fri 1/19/18 Mon
2/19/18
2.1 Accumulating the resources required for the
project 5 days Fri 1/19/18 Thu
1/25/18 7
2.2 Project Charter is formed 3 days Fri 1/26/18 Tue 1/30/18 9
2.3 Initial Documents are formed 3 days Wed
1/31/18 Fri 2/2/18 10
2.4 Surveyance and market analysis is done 4 days Mon 2/5/18 Thu 2/8/18 11
2.5 Technical and Technology required for
project is applied 7 days Fri 2/9/18 Mon
2/19/18 12
3 Communication Planning Phase 6 days Tue
2/20/18
Tue
2/27/18
3.1 Communication Medium is selected 1 day Tue 2/20/18 Tue 2/20/18 13
3.2 Roles of the Project Stakeholders are
developed 2 days Wed
2/21/18
Thu
2/22/18 15
3.3 Communication Strategies are applied 2 days Fri 2/23/18 Mon
2/26/18 16
3.4 Approval of communication plan 1 day Tue 2/27/18 Tue 2/27/18 17
4 Risk Management Phase 14 days Wed
2/28/18
Mon
3/19/18
4.1 Risk Factors are analyzed 4 days Wed
2/28/18 Mon 3/5/18 18
4.2 Risk Assessment is developed 3 days Tue 3/6/18 Thu 3/8/18 20
<<Name of the Student>> Page 5

INTRODUCTION TO SYSTEM DESIGN
4.3 Risk Analysis is formed 2 days Fri 3/9/18 Mon
3/12/18 21
4.4 Controlling Factors are developed 3 days Tue 3/13/18 Thu
3/15/18 22
4.5 Risk Management Plan is applied 2 days Fri 3/16/18 Mon
3/19/18 23
5 Plan Development Phase 18 days Tue
3/20/18
Thu
4/12/18
5.1 Plan Methodology is selected 3 days Tue 3/20/18 Thu
3/22/18 24
5.2 Plan outline is formed 4 days Fri 3/23/18 Wed
3/28/18 26
5.3 Analysis of the project requirements 3 days Thu
3/29/18 Mon 4/2/18 27
5.4 Plan is reviewed 2 days Tue 4/3/18 Wed 4/4/18 28
5.5 Completion of the plan 5 days Thu 4/5/18 Wed
4/11/18 29
5.6 Plan is approved 1 day Thu
4/12/18
Thu
4/12/18 30
6 Design Phase 17 days Fri 4/13/18 Mon 5/7/18
6.1 Design Methodology is selected 1 day Fri 4/13/18 Fri 4/13/18 31
6.2 Design outline is developed 5 days Mon
4/16/18 Fri 4/20/18 33
6.3 Design Requirements are developed 3 days Mon
4/23/18
Wed
4/25/18 34
6.4 Design is completed 7 days Thu
4/26/18 Fri 5/4/18 35
6.5 Design is approved 1 day Mon 5/7/18 Mon 5/7/18 36
Table 1: Project Front End Schedule Showing WBS
(Source: Created by the author)
<<Name of the Student>> Page 6

INTRODUCTION TO SYSTEM DESIGN
0 - Development of Mobile
Sales Application for
Picoso
1 - Project Initial Phase
1.1 - Portfolio Strategy is
developed
1.2 - Product Strategy is
developed
1.3 - Project Team is formed
1.4 - Structure of the
organization is formed
1.5 - Roles are assigned to
the team members
1.6 - Norms are developed
2 - Documentation and
Resource Accumulation
Phase
2.1 - Accumulating the
resources required for
the project
2.2 - Project Charter is
formed
2.3 - Initial Documents are
formed
2.4 - Surveyance and market
analysis is done
2.5 - Technical and
Technology required for
project is applied
3 - Communication
Planning Phase
3.1- Communication Medium is
selected
3.2 - Roles of the Project
Stakeholders are
developed
3.3 - Communication
Strategies are applied
3.4 - Approval of
communication plan
4 - Risk Management Phase
4.1 - Risk Factors are
analyzed
4.2 - Risk Assessment is
developed
4.3 - Risk Analysis is formed
4.4 - Controlling Factors are
developed
4.5- Risk Management Plan is
applied
5 - Plan Development
Phase
5.1 - Plan Methodology is
selected
5.2 - Plan outline is formed
5.3 - Analysis of the project
requirements
5.4 - Plan is reviewed
5.5 - Completion of the plan
5.6 - Plan is approved
6 - Design Phase
6.1 - Design Methodology is
selected
6.2 - Design outline is
developed
6.3 - Design Requirements
are developed
6.4 - Design is completed
6.5 - Design is approved
Figure 1: Project WBS in chart view
(Source: Created by the author)
Topic 3: Recommendations to Picoso
Some recommendations to the project of implementing the mobile application are given below,
Use of Prince2 methodology: The use of Prince2 methodology would be helpful for easing the flow of
operations and developing the faster processing of the information. The methodology is applied for
developing specific project plan for the project.
Technological Advanced tools: The use of the advanced tools and technology would help Picoso in
developing their mobile application and implying it for their users.
Secured Payment option: The secured payment option would help the customers of Picoso in making
faster payments via mobile application without the fear of frauds and thefts.
User Friendly and Personalized Interface: The user friendly and personalized mobile applications
would be helpful in developing the customer’s experience and achieve customer satisfaction from the
application developed.
Conclusion
It can be concluded from the report that the mobile based applications are comparatively more
benefit to the users and organization when compared to the web based operations due to Faster
<<Name of the Student>> Page 7

INTRODUCTION TO SYSTEM DESIGN
Processes, Personalized Content, Instant Online/Offline Access, and Add-on Features. The project
planning for the project can be done by the use of the specific methodology and it had been shown as
WBS table and chart view in the report. The recommendations for the project of Picoso are use of
prince2 methodology, technological advanced tools, secured payment option, and user friendly and
personalized interface.
<<Name of the Student>> Page 8

INTRODUCTION TO SYSTEM DESIGN
Bibliography
Bharadwaj, A., Sawy, O. E., Pavlou, P. & Venkatraman, N., 2013. Digital business strategy: towards a
next generation of insight. s.l.:s.n.
Emms, M. et al., 2014. Harvesting high value foreign currency transactions from emv contactless
credit cards without the pin. Proceedings of the 2014 ACM SIGSAC Conference on Computer and
Communications Security, pp. 716-726.
Hunziker, D., Gajamohan, M., Waibel, M. & D'Andrea, R., 2013. Rapyuta: The roboearth cloud engine.
Robotics and Automation (ICRA), IEEE, pp. 438-444.
Kim, E., Lin, J. & Sung, Y., 2013. To app or not to app: Engaging consumers via branded mobile apps.
Journal of Interactive Advertising, Volume 13(1), pp. 53-65.
Maier, A., Baltsen, N., Christoffersen, H. & Störrle, H., 2014. Towards diagram understanding: A pilot
study measuring cognitive workload through eye-tracking. s.l.:International Conference on Human
Behaviour in Design 2014.
McWherter, J. & Gowell, S., 2012. Professional mobile application. s.l.:John Wiley & Sons. .
Saarijarvi, H., Mitronen, L. & Yrjola , M., 2014. From selling to supporting-Leveraging mobile services in
the context of food retailing. Journal of retailing and consumer services, Volume 21(1), pp. 26-36.
Schmit, B. A. & Dustdar, S., 2015. Model-driven development of web service transactions. Enterprise
Modelling and Information Systems Architectures, 1(1), pp. 46-55.
Wen, D. et al., 2014. In: June Gamification design for increase customer purchase intention in a mobile
marketing campaign app.. s.l.:Springer,cham, pp. 440-448.
Yampolskiy, M. et al., 2015. A language for describing attacks on cyber-physical systems. International
Journal of Critical Infrastructure Protection, Volume 8, pp. 40-52.
Zhao, Z. & Balague, C., 2015. Designing branded mobile apps. Fundamentals and recomendations,
Volume 58(3), pp. 305-315.
<<Name of the Student>> Page 9