CIS5302 Professional Skills For Business Analysis

12 Pages / 2,845 Words Published On: 07-10-2021

Questions:

Keeping Track of Your Geocaching Outings

When Wayne Johansen turned 16, his dad bought him a new Garmin handheld GPS system. His family had always enjoyed camping and hiking, and Wayne was usually the one who monitored their hikes with his dad’s GPS system. He always liked to carry the GPS to monitor the routes, distances, and altitudes of their hikes. More recently, though, he had found a new hobby using his GPS system: geocaching.

Geocaching is a high-tech version of the treasure hunts that most of us did when we were kids. Participants search for geocaches or caches that are small, hidden, waterproof containers that typically contain a logbook and perhaps a small item. When found, the participant sometimes gets instructions for the next move—to either enter information into a logbook or to look for the next cache.

As Wayne became more involved with his hobby, he discovered that there are many different kinds of activities for geocaching enthusiasts. The simplest ones are those that involve caches found by using GPS co- ordinates, although even some of these tasks can be difficult if the caches are well hidden. Some of the activities involve multipoint drops where there is a set of clues in multiple locations that must be followed to arrive at the final cache point. Some activities involve puzzles that must be solved to determine the coordi-nates of the final cache.

Before long, Wayne wanted to make his own caches and post them for people to find. He discovered that there were several Web sites with access to geocaching information, caches, and memberships. He joined one of the geocaching Web sites and used it to log his finds. But he decided he would like to create his own system for tracking all the information he had about his caches. Conveniently, Wayne’s older brother Nick, a college student majoring in information systems, was looking for a semester project for one of his programming classes. The two of them decided to develop a system to help Wayne keep track of all his geocaching activities.

In this case, you will go through the various core processes of an SDLC and perform some of the activities of a development project. The project is divided into tasks and sub-tasks, as was our Tradeshow System project. The daily assignments for this case should be considered as preliminary efforts and rough drafts. The objective of these assignments is to help you remember the overall approach to software development. Several assignments have been listed for each task to allow your instructor to select those that best meet the objectives of the course.

Task 0: Define the Vision

Either by yourself or with another class member, brainstorm all the functions this geocaching system might do. Keep it at a very high level. These activities closely relate to Core Process 1: Identify problem and obtain approval. Write a rough draft of the System Vision Document based on your brain- storming ideas.

Task 1: Plan the Project

Based on the scope and vision you described in the System Vision Document, divide the project into at least two separate subsystems that can be done in separate iterations. For example, perhaps a first version can run on a laptop, with a second version that includes mobile components for a smartphone. These activities are related to Core Process 2: Plan and monitor the project—what to do, how to do it, and who does it.

Sub-Task 1.1: Divide the system into at least two separate components or subsystems, which can be supported with two iterations. Briefly describe each.

Sub-task 1-2: Create a work breakdown structure that lists all the steps to complete the first iteration. Put a time estimate on each step.

Task 2: Define and understand the Requirements

On task 2, you want to get an overall view of what the system needs to do for Wayne. There are two pri-mary areas to focus on to obtain this high-level understanding of the system: a list of use cases and a list of domain classes. You could document this information in lists, but diagrams provide a visual representation that is often easier to remember and understand. These activities support Core Process 3: Discover and understand details.

Sub-task 2-1: Create a simple use case diagram from the list of use cases.

Sub-task 2-2: Create a simple class diagram from the list of classes.

Task 3: Define the user experience

These activities are a continuation of what you began in task 2. The objective here is to further define what Wayne will need and how he will actually use the system. You will determine exactly how each use case works—what steps and options are available with the use case and even what the display and data- entry screens will look like. These activities primarily support Core Process 3: Discover and understand details.

Sub-task 3-1: Select a single use case and identify the steps required to perform the use case

Sub-task 3-2: Make a workflow diagram of the selected use case.

Task 4: Develop the Software Architecture Design

The high-level software architectural design of the system generally includes decisions about how the sys-tem will be built and what the database will look like. Design is a technical activity that requires experience in programming, database development, and software architecture. These activities support Core Process 4: Design system components.

Sub-task 4-1: Design a preliminary database schema for the classes in this iteration.

Sub-task 4-2: Decide whether you will build a desktop system or a browser-based system. Write a couple of paragraphs listing the pros and cons of each alternative to defend your decision.

Task 5: Develop the Detailed Design and Program the System

You probably have had many class projects where you designed a system and then programmed it. These kinds of activities support Core Process 5: Build, test, and integrate system components. Write a paragraph describing what programming language(s) you would recommend and what development environment you prefer. For this answer, draw on your previous programming and development experiences.

Task 6: Test and Deploy the System

You may have had opportunities to perform comprehensive testing of your programming class projects, especially if you have developed systems that integrated with other systems. These activities support Core Process 6: Complete system tests and deploy solution. Obviously, you can only do this if you have programmed the system.

Sub-task 6-1: Write a paragraph describing the difference between programmer testing and user testing.

Sub-task 6-2: Look at www.geocaching.com, which is a commercial Web site. What other issues need to be addressed to deploy this type of Web site?

Answers:

Task 0: Vision Document

The proposed framework is a Geocaching System that depends on Web. The proprietor of the project is Wayne Johansen. This vision archive is comprise of data like framework necessities, issues in actualizing the prerequisites and potential answers for the issues. The report likewise holds the project scope.

The framework prerequisites can be isolated into two areas, for example, utilitarian and non-practical. The utilitarian prerequisites are as taking after.

User Login
Administrator Login
Registration of Users
Registration Approval
Geacaching Videos
Geachaching hints
Geocaches
Add, Update and Delete Data

The non-functional requirements are as following.

Security
Availability
Real time data flow
Scalability
Maintainability
Accessibility
Data integrity

The primary extent of the project is building up an electronic framework. Alternate extents of the project are actualizing appropriate security in the framework, gathering framework prerequisites and changing over those necessities to framework functionalities, testing the framework so that no holes in the framework capacities remain and sending the framework inside server.

The primary favorable position of enrollment is that it will enable the site to track the part exercises. Without appropriate data chain of command, the framework can't track records. The id that will be given to the client will be utilized as the way to store each procedure related data against individual client. Wayne will endorse the client enrollment and at exactly that point the last procedure of enlistment will be finished. It is not generally feasible for little frameworks to check the client's pre-presence as utilizing an alternate name and id can do the rest. Wayne can examine the inputted information and recognize on the off chance that somebody is attempting to upset the framework. This will enable the framework to diminish the storage room as though same client makes two records then Wayne can deny the second one.

The primary issues in the executing the framework usefulness is security and continuous information stream. These elements are exorbitant and regularly make issues. So as to actualize these necessities, Wayne needs to utilize experts who will keep up the framework. The most straightforward approach to determine the issue is putting the support obligation to the designers.

Task 1: Plan the Project

Sub-Task 1.1: System Components and Iteration

The project will be started with arranging stage. In that stage, the calendar of the project, spending estimation, extend group determination, and numerous more assignments. After the arranging is finished, the necessities are assembled. The business examiner remains the accountable for social event business prerequisites. These business prerequisites are given to the framework investigator. Framework examiner change over those into framework prerequisites and therefore prompting the functionalities of the framework.

Website: In the principal cycle, a site will be finished. The site will comprise of interface, site pages, database, organize server and some more. After the prerequisites are assembled, the designers will break down the framework necessities. As the application and site will speak to various capacities in an unexpected way, the improvement procedure will be distinctive. At to start with, the product outline graph will be executed. On the off chance that Wayne endorses the product outline then the UI planning will be started. The framework capacities will be actualized in ASP.net and JavaScript. The outlines are checked a few times. After the last endorsement comes the venture moves to improvement stage. In this stage the coding is done, the information base is created and the system server is planned. The created framework is sent to the testing group to test the framework. The testing group do different testing on the item to discover whether there are any detectable crevice or blunder. In the event that mistake exists, then the framework is sent for change with a report record holding the points of interest of the test outcome.

Mobile Application: The second iterative model is practically same as the clench hand one. Nonetheless, in this model, the versatile application utilizes the database created inside the principal cycle. As the functionalities and data gathering procedures will be same, there is no need of creating diverse database. Be that as it may, a few changes might be made in the database according to better working of the application. The plan and advancement stage are practically indistinguishable. The testing stage takes after a similar strategy. The sending will be done alongside the desktop application. Both the applications will be sent inside a similar server. At in the first place, the application will be produced for android application. The explanation for is the notoriety of the versatile application. At first the framework capacities will be accumulated that has been created in the cycle one. At that point the capacities will be changed into application perfect elements.

Sub-Task 1.2: Work Breakdown Structure

Work Breakdown	Activity	Start Date	End Date
3	Website Development	19/06/17	02/07/17
3.1	Website Design	19/06/17	23/06/17
3.1.1	Ware Frame	24/06/17	27/06/17
3.1.2	Interface Solution	28/06/17	29/06/17
3.1.3	Functionality Verification	30/06/17	02/07/17
3.2	Implementation	02/07/17	17/07/17
3.2.1	Coding	02/07/17	09/07/17
3.2.2	Database Development	10/07/17	14/07/17
3.2.3	Server Implementation	15/07/17	17/07/17
3.3	Testing	18/07/17	23/07/17

Task 2: Defining and Understanding Requirements

Sub-Task 2.1: Use Case Diagram

Sub-Task 2.2: Class Diagram

Task 3: Defining User Experience

Sub-Task 3.1: Steps to Perform Use Case

The steps required to perform the approve registration use case are as following.

Admin Signin
Accessing Registration Approval Page
Review a Request
Grant or Reject permission

Sub-Task 3.2: Work Flow Diagram

Task 4: Developing the Software Architecture Design

Sub-Task 4.1: Database Schema

Sub-Task 4.2: Desktop vs Browser Based Application

The main difference between the desktop based system and browser based system is the accessibility.

Desktop Based Application: This sort of use can be considered as the independent programming. The desktop applications can be sent on various equipment freely. The client need to download the total application or the loader and introduce the application inside the PC

The benefits of the desktop based application are it can be extremely secure, the desktop based application can be get to rapidly, the speed of the application will be speedier, the application can without much of a stretch utilize the equipment and system of the PC and the application is fit for running in low web association.

The cons of the application are it will be restricted to a solitary platform (for example, Windows or MAC) or just couple of renditions of the stage, the application just can be utilized if adequate memory is accessible, if the OS glitches then the application may demonstrate mistake and some more.

Browser based application: Each PC framework has some default web program. The program based application can be gotten to using the web program within the sight of not too bad web association

The upsides of the application are it can be utilized diverse stage if the program bolsters the program, distinctive client can get to the application from a few PC just utilizing the interesting id, a colossal group is available and less measure of exertion expected to build up the framework along these lines prompting minimal effort.

The detriments are it will be more inclined to digital assaults, as all the advance and application capacities will be put away in the web server, the application will set aside opportunity to stack and the improvement is low as JavaScript is just innovation.

Task 5: Use of Programming Language and Development Environment

Task 5.1: Programming Languages:

ASP.net, JSON and JavaScript will be used for developing the the software.

ASP.net: ASP.NET is considered as the collection of Web development equipments that the Microsoft offers. Applications such as Visual Web Developer and Visual Studio .NET allow Web designers and developers making dynamic web pages using a graphical user interface. Certainly, software developers can create their individual specific programs and scripts as well as combine it within ASP.NET pages. Irrespective of the fact that it often observed like a descendant to Microsoft's ASP programming technique, ASP.NET as well strengthens Jscript, Visual Basic.NET., .NET and various open-source programs like Perl and. ASP.NET is generated on the basis of the .NET system that provides an API for coders. The .NET enhance equipments can be used for making software regarding both the Windows functioning system and the online functions. Applications such as Visual Studio .NET provide a visual interface for engineers regarding making individual software that resembles .NET as a rational decision in terms of planning Web interfaces.

Together regarding an ASP.NET web page for functioning properly, it has to be shared with a Web server, which supports ASP.NET software. Internet Information Services or IIS of Microsoft is used for generating Web server through a broad margin and it is the most crucial phase for ASP.NET pages. At the time when there exist few open-source options available for Linux-based systems, the options often do not provide adequate support to ASP.NET programs.

Java Script: It is a scripting programming language that has been generated by the organization called Netscape for empowering Web developers for planning innovative solutions. Through it distributes enormous quantities of tools and compositions of the complete Java language, it was generated separately. Javascript is capable of functioning with HTML programs, thus authorizing Web developers combine individual solutions with dynamic imports. JavaScript is combined by several programming associations and is considered as an open source program that developers can utilize without purchasing rights. It is supported by late programs developed by Netscape and Microsoft. However, Internet Explorer strengthens a small part of the gathering, which is known as JavaScript.

JSON: JSON or JavaScript Object Notation can be considered as a lightweight data operate assembling language. This language is easy regarding individual for pursuing and composing. It used in the devices for parsing and creating applications. JSON is referred as yhe content setting that is completely language independent. However, it uses practices that are normal to software developers of the C-group of languages, including C++, C, Java, C#, JavaScript, Python, Perl, and many more. These characteristics create JSON a appropriate information interchange language.

JSON is created based on two frameworks:

Solitary requested rundown of classes. In many languages, this is recognized as a rundown, vector, display, or sequence.
An gathering of esteem/name collections. In distinct languages, this is recognized as a resistance, lexicon, record, struct, hash table, cooperative display, or keyed rundown.

All of these are internal exclusive frameworks. Regarding entire aims and objectives all improved programming languages support those in some form. It promises sound that a data management that is appropriate with programming languages similarly be identified on these frameworks.

Task 5.2: Development Environment:

The development environment will be consisting of GUI, communication, middleware and data layer.

Graphical User Interface Layer: the GUI Layer (here and there called the "frontend") adjusts upon the shaky fringe between the universe of PCs and the universe of individuals. Accordingly, it must play out the regularly complex errand of deciphering amongst human and scripting languages. In its part as interpreter, the GUI is in charge of two things. To begin with, the GUI must interpret the longings, expectations, needs, and needs of individuals into executable, intelligent machine directions. In the meantime, the GUI should likewise make an interpretation of PC created information into significant comprehensible data. This interpretation, as you may envision, is no mean deed. Truth be told, in making web applications, web designers will invest the same amount of energy building a strong frontend as they will spend building up a reliable backend. As a web application designer, while fretting about the GUI Layer, you will in all likelihood be concerned essentially with the utilization and control of "UI Widgets" or "controls". Gadgets are interface devices that customers can use to make their aims, wishes, and needs known to the program. Gadgets could incorporate catches, scroll bars, matrices, or even interactive pictures. Gadgets ought to be practically instinctive to you as this is the bit of programming we people frequently work with. Generally, on the off chance that you see another innovation, you can remember it to be a GUI innovation in the event that it enables you to make interfaces comprised of gadgets and enables you to get to those gadgets as vital.

Communication Layer: After the client has presented whatever data they have to submit into whatever GUI you have planned, the time has come to understand that data from the web program to the web server. To do this, the data needs to go through the Communication Layer. There are a large group of advancements which all jab their way into the Communication Layer. Correspondence Layer is that data needs to get starting with one place then onto the next and that information needs to arrive in one piece, organized appropriately, and without any parts of that information changed or defiled. What's more, the data could/ought to be exchanged safely. That is, it ought to travel between various places without anybody having the capacity to peruse it, transform it, or fake initiation of it. Since there are such a large number of sorts of PCs thus numerous product bundles that must impart, you can envision that it every single simply work out to a mass of jabber. All things considered, to anticipate such bedlam, and to make the web work, everybody (programming and equipment) is required to take after exceptionally thorough gauges of interchanges called conventions. Conventions ensure that every member of the exchange can comprehend the other. For the reasons for the web, there are three sorts of interchanges conventions we think about:

Computer to PC correspondence - This is taken care of by the IP convention
Encryption of plain content over the wires - This is taken care of by a diverse of advancements yet most generally include some type of open key encryption.

Software to programming correspondence - Generally, TCP will move information from the equipment level to the product level. Once the information has been moved to the product level, the product bundles themselves will give their own conventions to correspondence. In the domain of web serves and programs, this is normally taken care of by HTTP or SSL on account of scrambled correspondence.

Task 6: Testing and Deploying System:

Sub-Task 6.1: User Testing vs Programmer Testing

User Testing: The client testing is the way toward testing an application or framework on the premise of how effectively a client is getting to the application or framework. In straightforward words, it is the method for testing how easy to use the web application is. The client testing is directed utilizing the genuine or potential clients of the application.

Programmer Testing: The developer testing technique is a traditional application testing strategy through which the individual source code units, sets of single or numerous PC program portions alongside the connected utilization designs, control information and operational procedures are tried.

Sub-Task 6.2: Deployment Issues

The essential issue in sending in this sort of site is the time. The venture is of low spending plan. Hence, the venture group cannot put much time in sending. On the off chance that any issue happens in the sending, the group settle the issue without understanding the center cause. This will to mistake in the application in life time.

Bibliography:

Alomari, E., Manickam, S., Gupta, B.B., Singh, P. and Anbar, M., 2014, February. Design, deployment and use of HTTP-based botnet (HBB) testbed. In Advanced Communication Technology (ICACT), 2014 16th International Conference on (pp. 1265-1269). IEEE.

Curino, C., Moon, H.J., Deutsch, A. and Zaniolo, C., 2013. Automating the database schema evolution process. The VLDB Journal, 22(1), pp.73-98.

Fernandez-Saez, A.M., Genero, M., Chaudron, M.R., Caivano, D. and Ramos, I., 2015. Are forward designed or reverse-engineered UML diagrams more helpful for code maintenance?: A family of experiments. Information and Software Technology, 57, pp.644-663.

Grozev, N. and Buyya, R., 2014. Inter?Cloud architectures and application brokering: taxonomy and survey. Software: Practice and Experience, 44(3), pp.369-390.

Kerzner, H., 2013. Project management: a systems approach to planning, scheduling, and controlling. John Wiley & Sons.

Kumar, B. and Singh, K., 2015. Testing uml designs using class, sequence and activity diagrams. International Journal for Innovative Research in Science and Technology, 2(3), pp.71-81.

Nanthaamornphong, A., Carver, J., Morris, K. and Filippone, S., 2015. Extracting uml class diagrams from object-oriented fortran: Foruml. Scientific Programming, 2015, p.1.

Ni, J., Li, G., Wang, L., Feng, J., Zhang, J. and Li, L., 2014. Adaptive Database Schema Design for Multi-Tenant Data Management. IEEE Transactions on Knowledge and Data Engineering, 26(9), pp.2079-2093.

Patwardhan, A., 2016. Analysis of Software Delivery Process Shortcomings and Architectural Pitfalls. arXiv preprint arXiv:1607.03748.

Schwalbe, K., 2015. Information technology project management. Cengage Learning.

Sharma, C., Sabharwal, S. and Sibal, R., 2014. Applying genetic algorithm for prioritization of test case scenarios derived from UML diagrams. arXiv preprint arXiv:1410.4838.

Storrle, H., 2014. On the impact of layout quality to understanding UML diagrams: size matters. In International Conference on Model Driven Engineering Languages and Systems (pp. 518-534). Springer International Publishing.

Whiting, S.W., Potenza, M.N., Park, C.L., Mckee, S.A., Mazure, C.M. and Hoff, R.A., 2016. Investigating Veterans’ Pre-, Peri-, and Post-Deployment Experiences as Potential Risk Factors for Problem Gambling. Journal of behavioral addictions, 5(2), pp.213-220.