Information Gathering for Use Case Model
The mobile applications are taking the whole digital word with storm. The easy to access feature, portability and internet access through Wi-Fi and mobile network made a mobile phone more effective than computers in accessing the net. The applications in mobile phones are faster and often save required data in mobile storage to provide services when mobile offline.
The Scene Brokers are intended in implementing a mobile application alongside with website. This report suggest information gathering methods, supports organization decision through scholarly articles and provide WBS.
Interview: It is one of the most used and versatile information gathering procedure. The project team will have a system analyst for doing the tasks of collecting requirements from the users. The analyst will select few persons, preferably at least a single person from each type of end users. The analyst will send invitation for interview to all those selected person. The participant will attend a one-to-one interview with the analyst. The analyst will pre-create a set of questions for the participant and ask them at time of interview. The interview questions will not be restricted to the prepared queries. Moreover, the analyst will be asking various other questions based on the answers and what information is required. The interview session will be more like a discussion on what is required and what can be provided.
Questionnaire: The questionnaire method is one of the most efficient methods for collecting a chunk of data in a very small time. The analyst will create set of questions for every type of users. These questions will be shared among the staff and customers of Scene Brokers. The questionnaire can be shared through Google forms, spread sheets, papers and many more ways. The participants will be providing answers through the same way and submit their response.
Evaluation of Documents: The Scene Brokers will assign an internal staff for assisting the analyst to look for organizational documents. The analyst will observe the documents that holds the information of how the business process data and generate information. After analysing the information, the can identify how the paper based manual works can be converted into virtual automation. The assistance will help the analyst whenever organization data will be difficult to understand for the analyst.
Use Case ID |
Primary Actor |
Use Cases |
UC-1 |
Business Customer |
Get register confirmation mail |
UC-2 |
Business Customer |
Pay Fee |
UC-3 |
Business Customer, Individual Customer |
Register |
UC-4 |
Individual Customer |
Welcome Mail |
UC-5 |
Business Customer, Individual Customer |
Login |
UC-6 |
Business Customer, Individual Customer |
Booking Details |
UC-7 |
Business Customer, Individual Customer |
Make Full Payment |
UC-8 |
Business Customer, Individual Customer |
Booking Confirmation Mail |
UC-9 |
Venue Providers |
Register Venue |
UC-10 |
Venue Providers |
Update Venue |
Use Case ID: |
UC-3 |
Use Case Name: |
Register |
Created By: |
Enter your name and student ID |
Date Created: |
03-01-2018 |
Actors: |
1. Business Customer 2. Individual Customer |
Description: |
The use case is considered as the system must have information about the end users. The outcome of the use case will be that system will have user name, type, login credentials and allocate them in a authorization level |
Trigger: |
A new customer wants to buy service from Scene Brokers |
Preconditions: |
The customer must not be registered before or the customer does not have bad history with Scene Brokers
|
Postconditions: |
The customer can have login credentials that can be used to login to the system |
Normal Flow: |
1. The business customer fill the data and pay annual charges 2. The system sends username, password and receipt for payment through mail 3. The individual customers only fills the forms and submit that form 4. The system sends a welcome mail by summarizing registration details |
Alternative Flows: [Alternative Flow 1 – Not in Network] |
The customer contacts with the administrator The administrator register them the same way |
Exceptions: |
A business may being stopped from registration due to previous inconvenience. The system will send the registration details to the admin and management of Scene Brokers. After their approval, the customer can register. |
Includes: |
1. Get register confirmation mail 2. Pay Fee 3. Welcome Mail |
Frequency of Use: |
The customers will use this process for the first time they want to connect with the application. |
Special Requirements: |
The system must define the authorization level of the user to improve security |
Assumptions: |
The customers will provide all the details The system will be able to identify all the false requests |
Notes and Issues: |
The system availability in between registration process is must. The system will store that mail is sent but due to server down it will not be sent. |
Mobile application will be fast: The mobile applications will be at least 1.5 time faster than websites (Kim, Wang and Malthouse 2015). As the major app structure will be downloaded into the mobile storage media, the applications only download database information. The data retrieve becomes very fast due this fact.
Benefits of Mobile Applications Compared to Websites
Personalized Contents: The end users of Scene Brokers will receive extremely tailored contents based on their preferences (Buller et al. 2014). It will be like providing the customers a tailored communication through the language they understand. The user centric preferences will enhance the customer satisfaction.
Instant Offline and Online Access: The mobile apps can store the vital data into the mobile storage media. The often accessed data are stored in the device so that least possible time can be used for showing crucial data (Ahmed et al. 2014). This makes the apps a crucial for business as the customers can see crucial data while they are offline.
Utilizing Device Features: The application of Scene Brokers can utilize the features that the user device can offer. The application can use the camera, scanner, NCF and more (Wunder et al. 2014). The application can use the other apps like payment apps for payments.
Push Notifications and Instant Updates: The push notifications are highly useful for Scene Brokers as the organization can communicate with the customer through the app even if the app is not open. The app can promote venues or other policies through the push notifications (Hu et al. 2015). The apps will be updated easily using the device app store. This will allow the customer to get the best experience from the application.
The usage of WBS: The work breakdown structure forces the project manager to create detailed steps of the project. This way the details steps will reveal more about the responsibilities of the project team members. The project manager can create better budget and schedule plans for the project. The project team will also be using the WBS for defining the scope of the project. They can measure, whether all the, scope of the project is achieved, using the WBS.
Conclusion:
From the above study it can be concluded that the mobile application will be a great choice for Scene Brokers for maintaining better relationship with the customer. The customer will be accessing the application more often than website. The organization can plan promotion in a more effective way now.
The Scene Brokers will be suggested to make application for both android and iOS so that all the users can get same priority. The application will have more security measures than website as mobile apps are more vulnerable.
Ahmed, E., Gani, A., Khan, M.K., Buyya, R. and Khan, S.U., 2015. Seamless application execution in mobile cloud computing: Motivation, taxonomy, and open challenges. Journal of Network and Computer Applications, 52, pp.154-172.
Buller, D.B., Borland, R., Bettinghaus, E.P., Shane, J.H. and Zimmerman, D.E., 2014. Randomized trial of a smartphone mobile application compared to text messaging to support smoking cessation. Telemedicine and e-Health, 20(3), pp.206-214.
Burns, A.C., Bush, R.F. and Sinha, N., 2014. Marketing research (Vol. 7). Harlow: Pearson.
Hajri, I., Goknil, A., Briand, L.C. and Stephany, T., 2015, September. Applying product line use case modeling in an industrial automotive embedded system: Lessons learned and a refined approach. In 2015 ACM/IEEE 18th International Conference on Model Driven Engineering Languages and Systems (MODELS) (pp. 338-347). IEEE.
Hu, X., Chu, T.H., Leung, V.C., Ngai, E.C.H., Kruchten, P. and Chan, H.C., 2015. A survey on mobile social networks: Applications, platforms, system architectures, and future research directions. IEEE Communications Surveys & Tutorials, 17(3), pp.1557-1581.
Kim, S.J., Wang, R.J.H. and Malthouse, E.C., 2015. The effects of adopting and using a brand’s mobile application on customers’ subsequent purchase behavior. Journal of Interactive Marketing, 31, pp.28-41.
Madanayake, R., Dias, G.K.A. and Kodikara, N.D., 2016. Use Stories vs UML Use Cases in Modular Transformation. International Journal of Scientific Engineering and Applied Science (IJSEAS)–Volume-3, Issue-1, ISSN, pp.2395-3470.
Reggio, G., Leotta, M., Ricca, F. and Clerissi, D., 2014, January. What are the used UML diagram constructs? A document and tool analysis study covering activity and use case diagrams. In International Conference on Model-Driven Engineering and Software Development (pp. 66-83). Springer, Cham.
Wildemuth, B.M. ed., 2016. Applications of social research methods to questions in information and library science. ABC-CLIO.
Wunder, G., Jung, P., Kasparick, M., Wild, T., Schaich, F., Chen, Y., Ten Brink, S., Gaspar, I., Michailow, N., Festag, A. and Mendes, L.L., 2014. 5GNOW: non-orthogonal, asynchronous waveforms for future mobile applications. IEEE Communications Magazine, 52(2), pp.97-105.
Zhai, C. and Lafferty, J., 2017, August. A study of smoothing methods for language models applied to ad hoc information retrieval. In ACM SIGIR Forum (Vol. 51, No. 2, pp. 268-276). ACM.