SRS Rate your day PROJECT FOR: TWO MINDS TECHNOLOGY STUDENT NAMES STUDENT ID INDERPREET KAUR MANGAT 30120626 RAJANAGARI DILIP REDDY 30132548 GURVIR SINGH VIRDI 30132186 SHAHID MANZOOR 30122508 Table of Contents 1. Introduction: 4 2. Overview of the Proposed System: 5 2.1 Scope of the Project: 5 2.2 Objective of the Project: 6 2.3 Acceptance Criteria: 6 2.4 Selection of Development Method and Justification: 6 2.5 Interaction with the External Environment: 8 2.4 Selection of Development Method and Justification: 8 2.5 Interaction with the External Environment: 10 3. Use cases and functional requirements 10 3.1 Use Case Diagram: 10 3.2 Business Rule and Context: 15 4. Non-functional requirements: 15 5 The limitations and constraints of the application are s following. 16 6. User Interfaces: 17 6.1 Home Page: 17 6.2 Sign In Page: 18 6.3 Registration Page: 19 6.4 Profile Page: 20 Context diagram 21 Data flow diagram 22 System Use Case Diagram 27 Activity diagram 29 ERD 31 Relational schema 32 Wireframe 33 Bibliography: 40 1. Introduction: The project management plan is a very crucial factor in the project management activity. The plan assists the project team to understand the whole application and working conditions. Along with the developer, the other stakeholders get the advantage of the project management plan. The project design phase is also a crucial phase in terms of application integration as this phase assists in recognizing the factors that are important for development. A structure of the project management team is the base of the project. If a project is ongoing then it is better to put the responsibility of individual task to the experts. This results in better working conditions and atmosphere. In order to maintain the team’s moral a person is appointed to handle the issues and manage project. This person is the project manager and remains at the top of the project team. The study includes the description of the application that rates the day of the users. This android application will rate the day of the user on daily basis. Within the study the project plan and design related activities such as deliverable of the project, UML and UI designs has been done. Project Team Structure: The project team will be consisting of project manager, designer, programmer and tester. The project manager is Inderpreet kaur. Inderpreet kaur is also responsible for creating the documentation. Mohammad shahid Manzoor is the application designer and have the job of creating the database of the system. Gurvir is the programmer who will develop the mobile applicaton. Finally, Dilip reddy is the tester. Client: The client of the project is Two Minds technology. Two Minds Technology Pvt. Ltd. powers the biggest platform for engineers & wannabe engineers. Faadoo engineers is the social forum for engineering user generated content. It is the biggest website for engineers in India. Engineering apps are one of the most highly downloaded Apps on engineering education. 100+ Apps, with 41k topics on engineering. Together the site and the apps boast of some good numbers. Client SIGN-OFF Date:____________________ Client name:_chandan ___________________ Project name:Rate your day ________________ Commissioned by:____________________ 2. Overview of the Proposed System: 2.1 Scope of the Project: i. Rating should be based on happiness scale ii. Provide motivational phrase iii. Provide report based on happiness scale analysis. iv. Developers should consider other factors for incorporation v. Should invite other people vi. Share the happiness result 2.2 Objective of the Project: The project objectives are as following. i. Delivering a system that can rate a user day ii. Delivering an application that is error free iii. Delivering an application that will analyse the user day regular basis iv. Delivering an application that is visually attractive v. Delivering an android application named “Rate Your Day’ 2.3 Acceptance Criteria: The acceptance criteria of the application are as following. i. The project will be delivering an fully functional and error free application ii. The project will be delivered within the deadline and budget iii. The developed system can create reports based on the stored data in the database 2.4 Selection of Development Method and Justification: The project is a small project and it is consisting of only four team members. The Waterfall Model is the best suited for the project development. Before the justification, it is important to discuss about the waterfall model. The waterfall model is consisting of six phases. These are as following, requirement analysis, system design, implementation, testing, deployment and maintenance. Within the system requirement gathering and analysis phase, the project manager identifies and develops all the system requirements. These requirements are documented carefully. With the design phase, the gathered requirements are analysed and various designs of the system are created. The implementation phase is the most important in the project as the application is actually developed in this phase. The testing phase assists in recognizing the existing gaps and documents the gaps. The documents are provided to the developers so that they can eliminate the issues in the system and re-send it for testing. The next phase is deployment. In this phase, the application is deployed in the working atmosphere of the client. After all the development related activity is done, then the maintenance phase occurs. The justifications for selecting the waterfall model are as following. i. As the project team is very small and project manager has relatively low knowledge in terms of experienced personnel, the waterfall fall model is the best suited. The waterfall model is a simple and easily understandable method that helps the project manger to concentrate on project rather than on method associated concerns ii. The waterfall model consists of deliverables and review for each phase. This project manager will be able to manage the project iii. As the proposed project is a small project, the waterfall model is the right one iv. The stages in the waterfall model are clearly defined. This assists the project manager to understand the project activities clearly 2.5 Interaction with the External Environment: Figure 2: The Context Diagram 3. Use cases and functional requirements 4. Non-functional requirements 5. Analysis Models 6. User Interfaces 2.4 Selection of Development Method and Justification: The project is a small project and it is consisting of only four team members. The Waterfall Model is the best suited for the project development. Before the justification, it is important to discuss about the waterfall model. The waterfall model is consisting of six phases. These are as following, requirement analysis, system design, implementation, testing, deployment and maintenance. Within the system requirement gathering and analysis phase, the project manager identifies and develops all the system requirements. These requirements are documented carefully. With the design phase, the gathered requirements are analysed and various designs of the system are created. The implementation phase is the most important in the project as the application is actually developed in this phase. The testing phase assists in recognizing the existing gaps and documents the gaps. The documents are provided to the developers so that they can eliminate the issues in the system and re-send it for testing. The next phase is deployment. In this phase, the application is deployed in the working atmosphere of the client. After all the development related activity is done, then the maintenance phase occurs. The justifications for selecting the waterfall model are as following. v. As the project team is very small and project manager has relatively low knowledge in terms of experienced personnel, the waterfall fall model is the best suited. The waterfall model is a simple and easily understandable method that helps the project manger to concentrate on project rather than on method associated concerns vi. The waterfall model consists of deliverables and review for each phase. This project manager will be able to manage the project vii. As the proposed project is a small project, the waterfall model is the right one viii. The stages in the waterfall model are clearly defined. This assists the project manager to understand the project activities clearly 2.5 Interaction with the External Environment: Figure 2: The Context Diagram 3. Use cases and functional requirements The Business Scenario: The user will first install the application within the mobile device. Then the user will try to login to the application. If the user is new, then he/she will register. After the registration, the user will login. After the login, the user will be redirected to the profile section. In the profile section, the user can rate the day, see the report of rating in terms of weeks, month or year. 3.1 Use Case Diagram: The fictional requirements of the system are as following. i. Create user profile---name, age(optional), gender(optional), email id, time to bed. ii. Edit profile iii. Rate your day iv. View weekly analysis report v. View monthly analysis report vi. View yearly analysis report vii. View comparative report viii. Login with Facebook ix. Share result on face book x. Invite users through Facebook xi. Record change in life or Enter notes with time stamp (should be relevant) xii. Display motivational phrase xiii. Display notification xiv. Check horoscope Use Case Name: Create User Profile Unique ID: User UC1 Area: User Profile Actor: User Description: The user will input the name, email Id, address and other data into the registration page and submit information through clinking on the sign-up button. Triggering event: A new user wants to access the application functions Trigger type: External Steps Performed Information for Steps User input data into the field User name, address, email and preferred password User Click on Submit button User name, address, email and preferred password The application sends the data to the database server User name, address, email and preferred password The server stores the data into the database User name, address, email and preferred password The user is redirected to the login page Login page link Preconditions: The user must not be registered into the database Post conditions: User has successfully registered Assumptions: Student has a compatible mobile device Requirements Met: Allows student to be registered into the system Outstanding issues: How many times a user can be allowed to register with other email id? Priority: High Risk: Medium Use Case Name: Rate Unique ID: User UC3 Area: User Profile Actor: User Description: The user will rate the day within the application Triggering event: The user is in the rating day section Trigger type: External Steps Performed Information for Steps The user enters into the rate your day section User Id The user clicks on the rate your day button with the input percentage User rating, Id The application sends the information to the database server User rating, Id The server stores the data into the database User rating, Id Preconditions: The user must have a valid user Id and password Post conditions: The user has successfully rated the day Assumptions: The user is providing the authenticated data Requirements Met: Allow the user to rate the day Outstanding issues: Should the application suggest some something for the user who continuously input low rating? Priority: High Risk: Low 3.2 Business Rule and Context: The business rules and contexts are as following. i. The organization will apply strong security measures for protecting the application from being hacked ii. The employee of the organization will not misuse the application in anyway iii. The consumer information will be disclosed to as minimal person as possible iv. The application will be analysed in every one month v. The database of the application will be refreshed or restored in every six months vi. The user who has not used the application for three months will automatically be erased from the database vii. No employee can register into the application viii. The application will not prioritize the users in any case 4. Non-functional requirements: The nonfunctional requirements of the system are as following. i. Availability: The system will be available for use 24*7. The users will be able to communicate with the main system and database through the installed application all the time. ii. Scalability: The application will adjust its use of resources as per the scale of business. If the users are more then it will use more resources and if the user quantity is low then lesser amount of resources will be used. iii. Security: As the application will be holding the information of connecting path to the database, it is very crucial to secure the application properly. The application will be using encryption method so that even after theft, the data cannot be read by the hacker. 5 The limitations and constraints of the application are s following. i. Long term based modification cannot be done in the application with the current objective ii. The possibility of the up gradation will end with the possibility of android iii. The application must be light weight as the targeted consumers may not want a heavy application for such a small purpose iv. It is never possible to secure the database completely as the data will be transferred through open internet connection or wifi v. Developed on JAVA for android vi. Simple responsive UL vii. Use minimalist modern GUL viii. Checked on several mobile devises 6. User Interfaces: 6.1 Home Page: 6.2 Sign In Page: 6.3 Registration Page: 6.4 Profile Page:   7. Context diagram Context level diagram is the high-level view of the project. It provides to resolve top to down approach. In rate your day app (Moodlytics), external entities are identified such as a user. The User can communicate with the system. The User can perform the variety of task such as creating, editing user information and viewing the analysis of the project. Context level diagram provides a high view level information for stakeholders. 7.1 Data flow diagram Dataflow explains about data process and transfer in product system. Graphical representation helps to identify source of data and its interaction with the other data sources and system within product frame. All this process help to reach common goal which is the output of system. 8. System Use Case Diagram 8.1 Activity diagram Activity diagrams are the graphical interpretation of system procedures. Activity diagrams describe the use cases, system functions and conditions in detail. 8.2 ERD 8.3 Relational schema ENTITY Attribute Comments USER Email_ID Primary key, Varchar Name Varchar Age Int Gender M,F Time to bed hh:mm PHRASE Phrase ID Primary key, int, auto inc. Phrase Varchar Author Varchar Rate Rate_ID Primary key, int, (1,2,3,4) Date dd/mm/yyyy ratting Char,(happy, very happy, average, dull) NOTE Note_ID Primary key, int,auto inc Rate_ID Primary key, foreign key Note Char Date dd/mm/yyyy Time hh/mm 8.4 Wireframe 9. Bibliography: Johnson, J. (2013). Designing with the mind in mind: simple guide to understanding user interface design guidelines. Elsevier. Page, T. (2014). Skeuomorphism or flat design: future directions in mobile device User Interface (UI) design education. International Journal of Mobile Learning and Organisation, 8(2), 130-142. Sharma, C., Sabharwal, S., & 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. Two Minds Technology. (2017). Two Minds Technology. Retrieved 12 May 2017, from http://twominds.co.in