Reference no: EM133450208

Tasks:

Given the popularity and successful growth of cloud computing (i.e., applications where the technology and the data are all stored on the Internet and users access the system via the Internet to perform necessary tasks), you will pick one cloud computing mobile application targeted at consumers or enterprises and conduct a planning exercise for it. Example solutions could include cloud databases or data storage technologies, cloud HR applications, cloud salesforce, advertising, and marketing solutions, cloud document editing technologies, etc.

You will then reverse engineer the technology (go from what you see as a user of the underlying system components that it takes to build the technology) and answer the following questions.

1. What is the purpose of the software for the end user or client (who uses the software/system)? This is not a detailed list of functionalities, but rather a broad managerial vision or overview of what outcomes a user can achieve by using such a technology.

2. What is the business value of such a system for the firm that created it? Writing an executive summary in order to make a strong business case for why managers should support the building of the chosen system. You should discuss here possible revenue streams (if applicable), customer long-term value, loyalty, and what this system offers vis-à-vis competitors, etc. refer to the more detailed instructions for the executive summary.

3. What is the scope of the project - that is, what end-user functionalities will be included in the system? Examine the software to answer this question in detail - creating a list of the primary/main functionalities offered by the software. Remember the difference between functional requirements and non-functional requirements - focus on the former here. Additionally, list two functionalities that you'd like to see added, but that the firm has not yet implemented in the software.

4. Describe the system that will need to be created to provide the features identified above. This exercise is meant to help you think about IT systems and their components. Creating a graphical deliverable or outcome-oriented Work Breakdown Structure (WBS). Be sure to include three levels (e.g., 1.1.1, 1.1.2) in at least one branch in your tree diagram. Start by determining high-level groups of system-level deliverables that are necessary to complete the chosen system, and then decompose the group into smaller system components (e.g., architecture, databases, code modules, user interfaces, system interfaces, and any others that are relevant). Remember the WBS decomposition rules.

5. Then roughly estimate how long the project will take to complete. For software-related components, use the CoCoMO model provided in class. For non-software related tasks, roughly estimate task time (in hours), and finally compute the total estimated time (in months) for the selected software/system. You can add these hour estimates to the WBS chart itself.