Monday, October 28, 2013

Evernote - Midterm Exam Paper




POLICARPIO, David Benjamin T.
11195231
Evernote – Midterm Exam

1.       Use case Diagram


2.       Use Case Narrative
Identification summary
Title: Create Notes
Summary: This use case describes the steps on how to create a new note.
Actors:
1.     User – Creates a new note
Creation Date: October 10, 2013                   Date of UpdateOctober 28, 2013
Versionv1.0                                          Person in ChargePolicarpio, David Benjamin

Flow of Events

Preconditions:
1.     The user is already a verified member of the System.
2.     The user has already logged in to his/her account.

Main Success Scenario:
1.     User creates a new note through his/her device.
2.     User enters a title for the note.
3.     User enters the note description.
4.     User saves the created note.
U   System records data to the database
5.     Use case ends successfully.

Alternative Sequences:
3a. User attaches files to the note.
1.     User clicks the “add file” icon.
2.     User browses the selected file.
3.     User clicks the “attach” button to upload the selected file.

Error Sequences:
E2. User doesn’t have any title for the new note.
1. System prompts the user to input a title for the note.

Identification summary
Title: Delete Notes
Summary: This use case describes the steps on how to delete a note.
Actors:
1.     User – Deletes a note
Creation Date: October 10, 2013                   Date of UpdateOctober 28, 2013
Versionv1.0                                          Person in ChargePolicarpio, David Benjamin

Flow of Events

Preconditions:
1.     The user is already a verified member of the System.
2.     The user has already logged in to his/her account.

Main Success Scenario:
1.     User searches for a note through his/her device.
2.     User selects the searched note.
3.     User clicks the “delete” icon to delete the note.
4.     User clicks the “Confirm Delete” to fully delete a note.
5.     Use case ends successfully.

Alternative Sequences:
3a. User clicks “Cancel” to abort the delete process.
1.     User clicks the “Cancel” icon.

Error Sequences:
E2. User doesn’t have any note to delete.
1.     System prompts the user that there was no note deleted.



Identification summary
Title: Edit Notes
Summary: This use case describes the steps on how to edit a note.
Actors:
1.     User – Edits an existing note
Creation Date: October 10, 2013                   Date of UpdateOctober 28, 2013
Versionv1.0                                          Person in ChargePolicarpio, David Benjamin

Flow of Events

Preconditions:
1.     The user is already a verified member of the System.
2.     The user has already logged in to his/her account.
3.   The user has already created a note

Main Success Scenario:
1.     User searches for an existing note through his/her device.
2.     User selects a note that will be edited.
3.     User clicks the “Edit” icon.
4.     User makes changes within the note.
5.   User clicks the “Save” button to finalize the edited note.
6.     Use case ends successfully.



3.       Activity Diagrams
a.       Create Notes

                 b.     Edit Notes


4.       Problem – Solution Technical Writing
a.       Problems
                                                              i.      Employees, students, and businessmen have a hard time successfully executing plans and projects within a certain time allotment.
                                                            ii.      Bringing numerous researches, journals, papers, and other sorts of documents all at once can be very stressful for anyone who uses such.
                                                          iii.      Many tend to forget schedules, tasks, lists, and the like.
b.      Root Causes
                                                              i.      Poor compilation of documents
                                                            ii.      Print outs tend to be large and heavy when carried anywhere and takes up too much space.
                                                          iii.      One of the very basic reasons to such cases is because they often forget to bring their notes, schedules, lists, and such with them.
c.       Solutions
                                                              i.       An online storage for its users to easily save files and retrieve them anywhere and anytime, provided with an internet connection.
                                                            ii.      Taking advantage of the digital age, documents can be stored into devices, such as laptops, cellphones, and tablets, which are very compact and easy to carry.
                                                          iii.       For the users to automatically carry all reminders with them through cloud storage. Devices linked together through the application, automatically synchronize anything that is uploaded by any one of the devices.
d.      Objectives
                                                              i.       To help users be more organized with their files when they use Evernote which can also help them be more productive.
                                                            ii.      To provide Evernote users the ease of having their files with them through the use of synchronized cloud storage.
                                                          iii.      To be able to provide users accessibility of their files through all possible digital devices compatible with Evernote and with ease through automatic sync.
e.      Goals
                                                              i.      Objective 1
1.       To provide Evernote users the ease of having their files with them through the use of synchronized cloud storage.
2.       Having the customers to use Evernote as their primary mode of organizing and scheduling their personal and professional life.
                                                            ii.      Objective 2
1.       Providing Evernote users an automatic synchronization of their files, as soon as they are uploaded, to avoid the hassle of manual input on each available device of the user.
2.       Help Evernote users have their soft copy files anywhere and anytime and help the users have their own “digital planer” through the use of their mobile devices.
                                                          iii.      Objective 3
1.       To be able to carry their files through the lightest and most compact medium available to the users
2.       Providing users the easiest way to use or retrieve files on the go even without internet connection after syncing automatically.
f.        Benefits
                                                              i.      Tangible
1.       Efficient way of documenting
2.        Increases speed in organizing files

                                                            ii.      Intangible
1.       Improved organized planning
2.       Ease in work process

5.       Founder Interview


Phil Libin
Phil Libin is a Russian-born American entrepreneur and CEO of the Silicon Valley-based software company Evernote.[1]
Prior to joining Evernote, Libin founded and served as president of CoreStreet, a company that provided credential and identity management technologies to governments and large corporations. In 2009, CoreStreet was acquired by ActivIdentity,[2] now owned byHID Global.[3] Libin was also founder and CEO of Engine 5, a Boston-based Internet software development company acquired by Vignette Corporation (VIGN) in 2000. Post-acquisition, Libin served as principal architect and chief technologist for applications at Vignette.
Libin graduated from Bronx Science in 1989 and attended Boston University with a concentration in Computer Science,[4] but did not complete his degree.


Lessons Learned:
        I grew up going through life of being an entrepreneur in my own way. I loved business and earning money. As I grew I became more curious and ventured out on what it actually takes to start up a business. Thus, I came about with a System and Design Firm.
        What I learned from Phil Libin is basically his strive to push through all the hardships until he came about with Evernote. Since he didn’t finish his degree in Computer Science, he had a hard time getting a job and drew the setting of having a business will be the only way. Thus, he pushed trough everything and is now the CEO of Evrnote.
        Another that I’ve learned from him is the idea of creating a project/software/solution that would cater to the everyday routines or essentials of humanity. Not only on the purpose of IT-fying a task but making it easier for the user to process such tasks. This is basically the sole mission of IT professionals. We only have to conceptualize which human task should be targeted and be developed to be able to market to the public.
        Finally, I realized that most CEOs known are drop outs. I am not pointing to the assumption that I should drop out of school to be able to be a CEO and be rich. Only do I have to finish my schooling to be able to properly provide for the business. A business requires more than 100% effort and attention from its owners. It must be looked at in all aspects and in all times. The complexity of starting up a business is much less than maintaining a business and making it grow in time. Basically, it is the one that hit me since I have started my own business.

Wednesday, October 9, 2013

Use Case Narrative for Evernote


 Identification summary
Title: Create Notes
Summary: This use case describes the steps on how to create a new note.
Actors:
1.     User – Creates a new note
Creation Date: October 10, 2013                   Date of UpdateOctober 10, 2013
Versionv1.0                                          Person in ChargePolicarpio, David Benjamin

Flow of Events

Preconditions:
1.     The user is already a verified member of the System.
2.     The user has already logged in to his/her account.

Main Success Scenario:
1.     User creates a new note through his/her device.
2.     User enters a title for the note.
3.     User enters the note description.
4.     User saves the created note.
5.     Use case ends successfully.

Alternative Sequences:
3a. User attaches files to the note.
1.     User clicks the “add file” icon.
2.     User browses the selected file.
3.     User clicks the “attach” button to upload the selected file.

Error Sequences:
E2. User doesn’t have any title for the new note.
1. System prompts the user to input a title for the note.

Identification summary
Title: Delete Notes
Summary: This use case describes the steps on how to delete a note.
Actors:
1.     User – Deletes a note
Creation Date: October 10, 2013                   Date of UpdateOctober 10, 2013
Versionv1.0                                          Person in ChargePolicarpio, David Benjamin

Flow of Events

Preconditions:
1.     The user is already a verified member of the System.
2.     The user has already logged in to his/her account.

Main Success Scenario:
1.     User searches for a note through his/her device.
2.     User selects the searched note.
3.     User clicks the “delete” icon to delete the note.
4.     User clicks the “Confirm Delete” to fully delete a note.
5.     Use case ends successfully.

Alternative Sequences:
3a. User clicks “Cancel” to abort the delete process.
1.     User clicks the “Cancel” icon.

Error Sequences:
E2. User doesn’t have any note to delete.
1.     System prompts the user that there was no note deleted.



Identification summary
Title: Edit Notes
Summary: This use case describes the steps on how to edit a note.
Actors:
1.     User – Edits an existing note
Creation Date: October 10, 2013                   Date of UpdateOctober 10, 2013
Versionv1.0                                          Person in ChargePolicarpio, David Benjamin

Flow of Events

Preconditions:
1.     The user is already a verified member of the System.
2.     The user has already logged in to his/her account.
3.   The user has already created a note

Main Success Scenario:
1.     User searches for an existing note through his/her device.
2.     User selects a note that will be edited.
3.     User clicks the “Edit” icon.
4.     User makes changes within the note.
5.   User clicks the “Save” button to finalize the edited note.
6.     Use case ends successfully.