2.2.2 Empathy Summary Canvas
It consists of five key parts:
1. First part is for user. In this section, we need to specify about the main user of the utility. The main user of this utility is the Administrator only.
2. Second part is for stakeholders. In this section, we write the stakeholder who is relevant to the user. In project, the main user is the administrator and the employees could be the stakeholders as they are relevant to the activities.
3. Third part is for Activity which is related to the user and stakeholders. Example - Monitoring. All the activities in cluding file renaming, searching a file, find the location, etc.
4. Fourth part is for a happy story. In this section, we write two happy stories which are related to the project. …show more content…
• Product Experience –We want a utility which could do all the above mentioned tasks with easy and fast access.
• Product Functions - Product functions deliver the product experience.
• Product Features – It includes a LAN network, Win OS 10, and a database.
• Components –These include the database, three tools and LAN.
• Customer Revalidation – The customer can revalidate the search functions, the speed and response time and the ease of use of this utility.
• Reject/Retain/Redesign – We can redesign the User Interface so that it matches the User’s needs for ease of use. We retain the functions as they are all required by the users.
2.3 System Design and Modelling Diagrams
The system design and modelling diagrams help us to better understand the system for which we will be coding for in the next phase.
The following diagrams show how the user would act and interact with the system and the various activities that user would perform:
2.3.1 NOTATIONS
DATA FLOW …show more content…
4.2 Usefulness with respect to existing solutions
Until now there were no single utility consisting of these three tools. There are many similar utilities which are successfully working individually for private use.
Our system consists of SQLite database which requires no installation, no extra drives, extensible up to 4B, unlimited backup and NDT framework.
4.3 Scope of future work
Currently we have performed renaming a single file in C# .net as we are learning along with the implementation needs. Once we complete this utility in the next semester, we may also think about improvements that the users need in the next versions and updates of the utility.
4.4 Unique Features of Our Innovation/Project
Our project implements a unique and user friendly utility on .net framework 4.6 that meets the requirements and needs of the users and the department.
Other utilities on other platforms had only provided functioning of a particular type, but we are merging the three similar utilities as an executable file under IT
It consists of five key parts:
1. First part is for user. In this section, we need to specify about the main user of the utility. The main user of this utility is the Administrator only.
2. Second part is for stakeholders. In this section, we write the stakeholder who is relevant to the user. In project, the main user is the administrator and the employees could be the stakeholders as they are relevant to the activities.
3. Third part is for Activity which is related to the user and stakeholders. Example - Monitoring. All the activities in cluding file renaming, searching a file, find the location, etc.
4. Fourth part is for a happy story. In this section, we write two happy stories which are related to the project. …show more content…
• Product Experience –We want a utility which could do all the above mentioned tasks with easy and fast access.
• Product Functions - Product functions deliver the product experience.
• Product Features – It includes a LAN network, Win OS 10, and a database.
• Components –These include the database, three tools and LAN.
• Customer Revalidation – The customer can revalidate the search functions, the speed and response time and the ease of use of this utility.
• Reject/Retain/Redesign – We can redesign the User Interface so that it matches the User’s needs for ease of use. We retain the functions as they are all required by the users.
2.3 System Design and Modelling Diagrams
The system design and modelling diagrams help us to better understand the system for which we will be coding for in the next phase.
The following diagrams show how the user would act and interact with the system and the various activities that user would perform:
2.3.1 NOTATIONS
DATA FLOW …show more content…
4.2 Usefulness with respect to existing solutions
Until now there were no single utility consisting of these three tools. There are many similar utilities which are successfully working individually for private use.
Our system consists of SQLite database which requires no installation, no extra drives, extensible up to 4B, unlimited backup and NDT framework.
4.3 Scope of future work
Currently we have performed renaming a single file in C# .net as we are learning along with the implementation needs. Once we complete this utility in the next semester, we may also think about improvements that the users need in the next versions and updates of the utility.
4.4 Unique Features of Our Innovation/Project
Our project implements a unique and user friendly utility on .net framework 4.6 that meets the requirements and needs of the users and the department.
Other utilities on other platforms had only provided functioning of a particular type, but we are merging the three similar utilities as an executable file under IT