Use Case Narrative and Activity Diagram

Christoper G. Hituro

Use Case Narrative : Update Profile

Identification Summary

Title: Update Profile

Summary: This use case describes the steps for update profile

Actors:

1.                      1. Users – update profile

2.                      2. System – update the system.

Creation Date: October 9, 2013                                                       Date of Update: October 9, 2013          

Version: v1.0                                                                             Person in Charge: Christoper G. Hituro

Flow of Events

Pre-Conditions:

1.                    1.  The User should have an account in order to access the website.

2.                    2. The User has successfully login to the website.

Main Success Scenario:

1.                     1. The user should click the drop down list besides the ‘Me’ icon

2.                     2.The user should click the view profile

3.                     3. The system response to the request to of the user to go to the Profile page.

4.                     4. The user clicks the update profile button.

5.                     5. The user fills-up the information or fields that are required.

6.                     6. The user click the save button.

7.                     7. The system should save all the information of the user.

8.                     8. Use Case ends successfully.

Alternative Sequence:

A5: Not required Fields

1.                      1.The user didn't put information in some fields because it’s not required.

2.                      2. User proceeds to step 6.

3.                      3. Use case ends

Error Sequence:

A6: Unable to save information

1.                       1. The user’s information was added.

2.                       2. Use case end.

Post-Conditions:

1.                        1. User information added.

Use Case Narrative: Practice Programming

Identification Summary

Title: Practice Programming

Summary: This use case describes steps associated to Practice Programming

Actors:          

1.       Users – Practice Programming
2.     .  System – show all the results

Creation Date: October 9, 2013                                                Date of Update: October 9, 2013

Version: v1.0                                                                             Person in Charge: Christoper G. Hituro

Flow of Events

Pre-condition:

1.      . The user should have an account to the website in order to access it.
2.      .  The User has successfully login to the website.

Main Success Scenario

1.        The system will show all the programming language to the user.
2.        The user can select the programming language he/she wants to practice.
3.        The user should create codes according to what the instruction is.
4.        The users click the next button.
5.        The system will verify if the codes are correct.
6.     Use case ends successfully.

Alternative Sequence:

A2: Choosing another language

1.    The user can choose another programming language if he/she don’t want to continue the language he/she choose.

2.     Follow steps 3-5.

3.                           3. Use case ends.

A5: Correct codes

1.    . The system will automatically go to the next exercise.
2.     . Do step 3-5.
3.    . Use case ends.

Error Sequence:

A5: Invalid codes

1.      The user gives invalid codes.
2.      The system will show an error notification to the user.
3.       The users go back to the codes and try another code.
4.        Use case ends.

Post-condition:

1.     . The user will get points after finishing the language.
2.     .  The user will get badges.

Use Case Narrative:   View Badges

Identification Summary

Title: View Badges

Summary: This use case describes the steps on how to view badges of the users.

Actors:

1.        Users – The one who view badges
2.        System – Show all the badges of the user.

Creation Date: October 10, 2013                                               Date of Update: October 10, 2013

Version: v1.0                                                                             Person in Charge: Christoper G. Hituro

Flow of Events

Pre-condition:

1.        The user should have an account in order to access the website.
2.        The user has successfully login to the website.

Main Success Scenario:

1.        The user should click the drop down list beside the ‘Me’ icon.
2.        The user should go to view profile.
3.        The user click the badge link
4.        The system will show the badges that the user has.
5.        Use case ends successfully.

Alternative Sequence:

A4: Show badges

1.        Use case ends.

Error Sequence:

1.       Use case ends.

Post-condition:

1.     .   The user will know how many badges he/she has.

DOCUMENTATION

Having knowledge about the importance of documentation in every aspect of our lives was a very big accomplishment to us. Documentation is like telling someone a story, giving directions, showing step-by-step process, etc... but not in a verbal manner. Documenting something was very important because it might help the other people who want to learn something new that can help them answer their questions. Here are examples of how documentation affects our lives. Tupe wants to learn how to draw, he can look for different books about sketching, drawings and paintings, and he can also watch video tutorials so that he can learn more techniques on how to draw. As he continues doing it he became expert and able to draw amazing drawings. Another example, a guy wants to know all the details about cars. He can search for books, and videos all about cars. There are few examples of a big significance of documentation to us. As you can see there are a lot of examples of documentation that is related to a simple life of a person. Maybe it is a form of a step-by-step process or maybe in a form of a informative materials, maybe it show us direction like a map. So many use of documentation, maybe we didn't know or notice that our everyday living has an aspect of documentation.

 Being good in documentation is a key to a good document. Before you become good at documenting, you should know how to construct a simple documentation. This will help you to enhance more and you should also good at vocabulary so that you can use different words that fit in your documentation. Having high-quality documentation is very important, because the users can understand and learn to a high quality documents. It can give more details and information to the users, it can also elaborate the thing that is needed for the users to understand deeply. As I've said earlier you can only achieve a high-quality if you know how to construct a simple document. As you practice in documentation you gain more knowledge, techniques, and ways to create high-quality documentation. 

The lesson I've learned from the post was, documentation is everywhere we cannot escape it. It has a really big role to our lives and to the society. Learning about documentation was very significant to me, because documentation is my weakness; I am not good at it. I've also learned that documentation has four parts which is "First Contact", "The Black Triangle", "The Hairball" and "The Reference". These leanings can help me in my Course because IS was a course that is associated of many documentation subjects and because of these new knowledge maybe I can overcome my weakness and pass the subjects that is related to documentation. 

September 11, 2013