Slideshare

In partial fulfillment of Sysanal, this post will sum up the learnings I have acquired during the first half of the term. This post will show the Use-case diagram, use-case narrative and an interview session of the founder of my assigned website,  Slifdeshare. I hope the readers of this post will find this informative 

1.      1.  Transaction Processing System (TPS)

TPS is a computerized system that performs and records daily routine transactions. Similar to TPS, Slideshare records the activities that are being done by the user in Slideshare. For example, in the flashed picture, it can be seen that the time it was posted as well as the number of times the post was viewed was recorded. These information that are recorded are already forms of transactions. 

1.   2. Office Automated System (OAS)

Office Automated System is a “paperless” office which is actually the main function of Slideshare. Through Slideshare its users are able to upload office outputs such as Powerpoints, Word Documents, PDFs and many more and then share it to the public for them to use. 

Podcast of Founders

(Since there were no available videos of any interview of the founders of the Slideshare, here's the link to the podcast of  the founders of Slideshare sharing their story of success) 

1.       Jonathan Boutelle and Rashmi Sinha who were the founders of Slideshare had a vision. They knew from the very beginning that what they are doing is business. Their vision of making this business work made them successful in launching Slideshare. A vision is what or where you foresee yourself in the future.  From them I have learned that vision is that main element that will keep you focused and determined to achieve your goal.

2.       Another key to the success of Slideshare probably came from the fact that Jonathan and Rashmi focused on what their audiences wanted. During the time when they started Slideshare, there weren’t really a site where users can upload their presentations and directly get the links for them to post it on their blogs (since according to these founders, during those times blogging and social media was already a hit). From there, they knew that their target audiences wanted and needed, so that’s what they focused on creating.

3.       Finally, Jonathan and Rashmi were open to a lot of possibilities. They did not stick on to one specific idea, they were very versatile.  Their ideas were growing which was another aspect that brought them closer to their vision.

Summing up the three main things that I have learned from them, basically all of them are kind of like tips on how to start up a business. Jonathan Boutelle and Rashmi Sinha’s story can definitely inspire aspiring young entrepreneurs to have a vision, to focus on what their target audiences want and need and to be open to a lot of different ideas that may possibly bring them closer to their vision. 

Identification Summary (1) 

Title: Post Photos on Tumblr
Summary: This use case describes the steps associated with posting photos on Tumblr.
Actors: 
   1. Blogger
   2. Tumblr
Creation Date: October 18, 2013                 Date of Update: October 18, 2013
Version: v1.0                                                Person in Charge: Blogger

Flow of Events

Preconditions:
   1. Blogger has an existing account in Tumblr.
   2. Blogger has already logged in to his account in Tumblr.
   3. Blogger is browsing through his computer.

Main Success Scenario:
   1. Blogger clicks on the Camera icon on his page.
   2. Blogger chooses to post existing photos.
   3. Tumblr open a window where Blogger can locate his photos.
   4. Blogger locates his photos.
   5. Blogger chooses the photos he will post.
       Step 5 repeats until Blogger finalizes the photos he will post or when he reaches the maximum of 10              photos.
   6. Blogger may or may not write descriptions and tags for his photo/s.
   7. Blogger publishes his photo/s.
   8. Use case successfully ends.

Alternative Sequence:
  A2 a. The Blogger chooses to take a photo
   1. Blogger chooses the take photo option on Tumblr.
   2. Tumblr asks Blogger if it can use its computer's camera.
   3. Blogger allows Tumblr to use his camera.
   4. Blogger takes a normal or gif photo.
   5. Proceed to step 6.

A2 b. The Blogger chooses to post photo using a URL
   1. Blogger copies the URL of the photo he wants to post.
   2. Blogger pastes the URL of the photo to Tumblr.
   3. Proceed to step 6.

  A5. The Blogger deletes or changes the photo he has already chosen.
   1. Blogger clicks on the "x" button on the upper right corner of the photo he has chosen.
   2. Proceed to step 5.

Error Sequences:
  E4. Location of photos cannot be found.
   1. Blogger cancels posting of his photo/s.
   2. Use case ends.

  E7. Blogger clicks close button instead of publish.
   1. Selected photos will be void and windows for posting photos will close.
   2. Use case ends.

Post Conditions: 
   1. Photo/s are posted on Blogger's Tumblr page.
   2. Tumblr page updated.

UI Requirements: 
   1. Tumblr ________________________________________________________________________________

Identification Summary (2) 

Title: Follow Another Blogger
Summary: This use case describes the steps associated with following another Blogger on Tumblr.
Actors: 
   1. Blogger
   2. Tumblr
Creation Date: October 18, 2013                 Date of Update: October 18, 2013
Version: v1.0                                                Person in Charge: Blogger

Flow of Events

Preconditions:
   1. Blogger has an existing Tumblr account.
   2. Blogger is logged in to his personal Tumblr account.
   3. Blogger is browsing through his computer.

Main Success Scenario:
   1. Blogger clicks on the "Find Blog" link on his homepage.
   2. Tumblr opens to a page where Blogger can choose the kind of blog he is interested in.
   3. Blogger chooses the genre of blog he wants.
   4. Tumblr displays blogs in the chosen genre.
   5. Blogger clicks on the blog he wants.
   6. Tumblr opens the webpage of this chosen blog.
   7. Blogger clicks on the follow button at the upper right corner of the page.
       Steps 3 to 7 repeats until Blogger is done following other bloggers.
   8. Use case successfully ends.

Alternative Sequence:
  A1. Blogger decides to look for other blog via search tab.
   1. Blogger types in the blog URL or the tags og the blog he specifically wants to follow.
   2. Proceed to step 7.

  A5. Blogger clicks on a blog he doesn't like.
   1. Blogger returns to the selection of blogs.
   2. Blogger chooses the blog he wants.
   3. Proceed to step 6.

  A7. Blogger wants to unfollow blog.
   1. Blogger goes to the blog he wants to unfollow.
   2. Blogger clicks on the unfollow button on the upper right corner of the page.
   3. Proceed to step 7.

Error Sequences:
  E3. Blogger cannot find a blog he wants.
   1. Blogger browses through the selection of blogs in the genre he wants.
   2. Blogger fails to see interesting blogs.
   3. Blogger decides not to follow any new blogs.
   4. Use case ends.

E6. Page of the blog the Blogger wants to follow won't open.
   1. Blogger chooses the blog he wants to follow.
   2. Tumblr detects error in the blog.
   3. Blogger closes the webpage.
   4. Use case ends.

Post Conditions: 
   1. List of following people (blog) updated.
   2. Tumblr page updated.

UI Requirements: 
   1. Tumblr
_________________________________________________________________________________

Identification Summary (3) 

Title: Reblog Posts
Summary: This use case describes the steps associated with reblogging posts on Tumblr.
Actors: 
   1. Blogger
   2. Tumblr
Creation Date: October 18, 2013                 Date of Update: October 18, 2013
Version: v1.0                                                Person in Charge: Blogger

Flow of Events

Preconditions:
   1. Blogger has an existing Tumblr account.
   2. Blogger is logged in to his personal Tumblr account.
   3. Blogger is browsing through computer.

Main Success Scenario:
   1. Blogger browses on posts on his dashboard.
   2. Blogger finds a post he wants to reblog.
   3. Blogger clicks on the reblog button.
   4. Tumblr opens the post Blogger wants to reblog on a new window.
   5. Blogger may or may not write a descriptions and/ or tags on the post he wants to reblog.
   6. Blogger clicks on the reblog button.
   7. Tumblr posts the reblogged post on Blogger's blog.
       Steps 1 to 7 repeats until Blogger decides to stop reblogging.
   8. Use case successfully ends.

Alternative Sequence:
  A1. Blogger is looking at blogs which are not in his dashboard.
   1. Blogger browses posts from other blogs.
   2. Blogger clicks on the post he wants to reblog.
   3. Blogger clicks on the reblog button at the upper right corner of the page.
   4. Proceed to step 4.

Error Sequences:
  E2. Blogger cannot find a post he wants to reblog.
   1. Blogger cannot find any post he wants to reblog.
   2. Blogger decides not to reblog anything.
   3. Use case ends.

  E6. Blogger accidentally clickes the close button instead of the Reblog button.
   1. The post the Blogger wants to reblog will be void.
   2. The window of the post to be reblogged will be closed.
   3. Use case ends.

Post Conditions: 
   1. Dashboard is updated.
   2. Tumblr page updated.

UI Requirements: 
   1. Tumblr

UCL of Tumblr

Systems Analysts

 

If I were to describe the characteristics of systems analysts, they would be individuals who are creative and innovative thinkers who are not afraid of change. They are those people who understand business as well as technology. Given that, I would say that systems analysts should definitely be technical. Without them being technical, their capability to think outside the box would be limited. In my opinion, the technical side of systems analyst is the main source of their growth, without it an improvement will be a challenge to make and problems that are supposed to be solved by them might be left unsolved.

     Systems analysts as mentioned earlier are these rare individuals who are knowledgeable in both business and technical fields. Not a lot of job roles can perform the way a systems analyst can. Take for example a software engineer, it is IT related, however it focuses mainly on software development. The software developed by these software engineers may be the ones needed by the businessmen however before these businessmen make use of these software, systems analysts would need to analyze first the systems used by these businessmen.  Systems analysts serve as the bridge that connects the software engineers and businessmen for they possess both technical and business skills. In addition, in any case that a systems analyst decides to shift its course of career and focus on either business or on being completely technical, they can still perform a number of roles because systems analysts are very versatile in nature.   

     I think the different systems which are assigned to specific groups on the organizational pyramid to maximize the efficiency of each group. It is strategically organized in such a way where each member of the group may perform according to their forte so that their group may perform effectively. It is important for each group to function as best as they could because each group is a subdivision of an entire system, thus if a group within the system is not organized based on their functionality, it may collapse causing a bigger trouble to the entire system. For example the Management Information System, this system’s output is a summary report. Management Information System obtains data from the Transaction Processing System which is the computerized system that performs and records the daily routine transactions necessary to conduct of the business, since the Management Information System depends on the stored data from the Transaction Processing Systems it Management Information System would not be able to produce its output if the Transaction Processing Systems fail to perform its task properly. 

       The Waterfall Model and Agile both have pros and cons when it comes to their functionality. Basically, a Waterfall model emphasizes on a definite, clear and well thought of plan before executing any kind of development and is extensively documented. On the other hand, Agile is more flexible in such a way that it promotes adaptive planning and evolutionary development. Personally, any of the two methods can be better than the other depending on the kind of project these models will be used. Waterfall models I think are better used in projects wherein there are minimal possible changes in the process since it is more challenging to make changes once major errors or changes occur. However with Agile, although it is very versatile it does not have a structure unlike the Waterfall model. Majority of the time, it is more difficult to predict the outcome of a project if it has no concrete plan. Hence, it is better to find out which method is more appropriate for a project before using them. In my opinion, Waterfall Model should be used in big projects with higher stakes since big projects need extensive planning before executing while Agile method can be used with the smaller projects where constant changes are more manageable.

     I think a great interview is when the purpose of the interview is achieved after it. It should make the interviewers feel more knowledgeable about their topic after the interview. While a great interviewer is someone who is able to make smart and sensible questions that are essential in clarifying the subject of the interview. In addition, a great interviewer is someone who observes proper behavior while conducting the interview. 

Works Cited

Agile Introduction for Dummies. (2008, January). Retrieved October 4, 2013, from Wordpress: http://agileintro.wordpress.com/2008/01/04/waterfall-vs-agile-methodology/

Mikoluk, K. (2013, September 9). Agile Vs. Waterfall: Evaluating The Pros And Cons. Retrieved October 4, 2013, from udemy/blog: https://www.udemy.com/blog/agile-vs-waterfall/