Friday, November 22, 2013
Friday, November 8, 2013
Obtain Barangay Clearance
UCN
Title: Obtain Barangay Clearance
Summary: This use-case describes
steps associated with obtaining a barangay clearance.
Actors:
- Student
- Barangay Staff
- Barangay Secretary 1
- Barangay Secretary 2
- Barangay Captain
Creation Date: November 8, 2013 Date of Update: November 8, 2013
Version: V1.0 Person-in-Charge: Jeane L. Paguio
Flow of Events
PRECONDITIONS:
1. Student has a valid ID
MAIN SUCCESS SCENARIO:
- Student goes to the Barangay Hall
- Student asks a Barangay Staff where to get the barangay clearance
- Barangay Staff directs Student to Secretary 1
- Student proceeds to Secretary 1
- Secretary 1 asks Student for a photocopy of Student’s valid ID
- Student submits the photocopy of the valid ID
- Secretary 1 asks Student to fill up information sheet
- Student fills out the information sheet
- Student submits the information sheet to Secretary 1
- Secretary 1 staples the information sheet with the photocopy of the valid ID
- Secretary 1 hands it over to Secretary 2
- Secretary 2 asks Student to sign in the barangay clearance
- Student signs in the barangay clearance
- Secretary 2 transfers the information from the information sheet in the barangay clearance
- Secretary 2 lets the Barangay Captain sign the barangay clearance
- Barangay Captain signs the barangay clearance
- Secretary 2 hands over barangay clearance to Student
- Student leaves the Barangay Hall
- Use- case successfully ends
ALTERNATIVE SEQUENCE:
A5.
Student has not yet photocopied the valid ID
- Student photocopies the valid ID
- Proceed to step 6
ERROR SEQUENCE:
N/A
POST CONDITION:
- Student claims the barangay clearance
_
ACTIVITY DIAGRAM
Friday, October 25, 2013
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.
(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.
Friday, October 18, 2013
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
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
Friday, October 11, 2013
Friday, October 4, 2013
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/
Friday, September 27, 2013
The Future of Systems Analysis
Systems Analysis as discussed in our class portrays
significant roles in our society. To fully understand the importance of systems
analysis, let us first define what systems analysis is. Basically systems
analysis from its name itself is about analyzing a system (Copley) .
It is the process of utilizing information to find out what the system needs in
order to efficiently meet the needs of its users. Systems analysis follows an
overall process in order to meet the needs of the users (Systems Analysis) .
This process starts from research
where the analyst collects information about the existing system, followed by
the analysis wherein examination of the present system works and identification
of problem happens. The design where coming up with a new and innovative idea
that can fix the existing system is followed by the production of the design.
After the design is produced, it is tested, documented, implemented and finally
evaluated. Examples of systems that undergo this process are systems used in
organizations or businesses such as the systems of communication, financial
systems, manufacturing systems and many more.
Different fields of businesses and companies make use of
systems analysis. Systems analysts are like the magical tool of these
businesses and companies who finds out the problems in their systems and
providing them innovative ideas on how to solve their problems. These
innovative ideas are influenced by the evolving technology in our society
today. Personally, I think systems analysis will improve even more and will
come up of even more creative ideas on how to meet the needs of the users of
these businesses and companies. I think that in the near future, systems
analysts will come up with solutions that are very convenient that might even
replace the human workforce. In order for a business to be globally competitive
they will have to continuously update their existing system especially today
that technology developing rapidly. This rapid development of technology is
brought about by the continuous improvements made by the systems analysis.
So what’s in store for systems analysis in the future? I foresee
systems analysis being even more in demand in the future knowing how important
it is to all kinds of businesses. Systems analysis would continue to improve as
technology develops for their improvements somehow depend on each other.
Systems analysis will exist even if technology stops improving but technology
cannot exist without systems analysis because through it problems are found and
solutions to these problems are made. Hence, following the direction of the
existing systems analysis we have today it is easy to see that it is going the
upward direction. Take for example the
products develop by Apple, in the past years gadgets which were touch screen can
only be seen in futuristic movies, now it is made available to almost everyone.
This technology would not be made possible if Apple stuck with the system it
used when the company was first established, Apple may have even closed a long
time ago if their systems were not developed. Apple will continue to improve
its systems to stay at the top of their game and to continue to be globally
competitive. Bottom line is that in whatever perspective you look at systems
analysis will never be taken out of the picture. It will continuously look for
a way to make existing systems improve making things as convenient and
efficient as possible to all of its users.
Works
Cited
Systems Analysis. (2013, September 26). Retrieved September 27, 2013, from Wikipedia:
http://en.wikipedia.org/wiki/Systems_analysis
Copley, S. (n.d.). What is Systems Analysis. Retrieved
September 27, 2013, from IGCESEICT: http://www.igcseict.info/theory/8/what/
Systems Analysis. (n.d.).
Retrieved September 27, 2013, from Merriam-Webster :
http://www.merriam-webster.com/dictionary/systems%20analysis
Subscribe to:
Posts (Atom)