Technical Writing
Topic: Groupon
Future of Systems Analysis
Friday, November 22, 2013
Friday, November 8, 2013
Use cases
Identification Summary
Title: Obtaining Barangay ClearanceSummary: This use case describes the steps involved in obtaining a barangay clearance.
Actors:
1. Applicant - requests the barangay clearance
2. Barangay Staff - files and prints the clearance
3. Barangay Captain - approves clearance
Creation Date: Nov. 8 2013 Date of update: Nov. 8 2013
Version: 1.0 Person in charge: Student
_________________________________________________________________________________
Flow of Events
Preconditions:
1. Applicant must have a valid government I.D.
2. Applicant must be a resident in the barangay
Main Success Scenario:
1. Applicant arrives at the barangay hall.
2. Applicant requests the barangay clearance from the barangay staff.
3. Barangay staff receives request.
4. Barangay staff requests applicants government I.D.
5. Applicant accomplishes requirements.
6. Barangay staff fills out missing information in the base copy of the clearance.
7. Barangay staff prints out the clearance.
8. Barangay staff hands print out to barangay captain.
9. Barangay captain approves clearance.
10. Barangay captain hands the clearance to applicant.
11. Applicant checks everything and signs the clearance to complete transaction.
Alternative Sequences:
A8. Barangay Captain is not present
1. Barangay staff double checks the paper personally.
2. Barangay staff hands clearance to applicant.
3. Proceeds to step 11.
Error Sequences:
1. None
PostConditions:
1. Applicant has a barangay clearance.
Obtaining a Barangay Clearance Activity Diagram
Friday, October 25, 2013
Use Cases
I.
Groupon sample Use Case Diagram
Groupon is a popular deal-of-the-day website that feature discounted offers that could be used at local or national companies.
II.
Users can obtain deals daily and Groupon updates their offers often
2. Groupon can also be classified as a DSS or Decision support system
Groupon also handles other business' marketing
IV.
Interview on Eric Lefkosky co-founder of Groupon
I learned from the interview that is important to build a solid base. An entrepreneur can't keep on pursuing bigger and better things if its base keeps crumbling. Another important lesson from the interview is very simple. You must keep firm and stay on course as your business morphs and shifts. Being persistent pays off. As the co-founder of Groupon states that mobile may be the next big thing I also agree to it. Something as small as an object that can fit in you pocket can have enormous potential. In the future more and more things can get integrated into our mobile phones such as mobile purchases. This could introduce the next big thing, the mobile market.
Photo Sources:
www.groupon.com
Groupon sample Use Case Diagram
Groupon is a popular deal-of-the-day website that feature discounted offers that could be used at local or national companies.
II.
Groupon from Irwin Dayak
III.
1. Groupon can be classified as a TPS or Transaction Processing system
III.
1. Groupon can be classified as a TPS or Transaction Processing system
Users can obtain deals daily and Groupon updates their offers often
2. Groupon can also be classified as a DSS or Decision support system
Groupon also handles other business' marketing
IV.
Interview on Eric Lefkosky co-founder of Groupon
I learned from the interview that is important to build a solid base. An entrepreneur can't keep on pursuing bigger and better things if its base keeps crumbling. Another important lesson from the interview is very simple. You must keep firm and stay on course as your business morphs and shifts. Being persistent pays off. As the co-founder of Groupon states that mobile may be the next big thing I also agree to it. Something as small as an object that can fit in you pocket can have enormous potential. In the future more and more things can get integrated into our mobile phones such as mobile purchases. This could introduce the next big thing, the mobile market.
Photo Sources:
www.groupon.com
Friday, October 18, 2013
Use Case Narratives
Identification Summary
Title: Report Project
Summary: By clicking the Report Project a user is attempting to
report the project to an admin and await for further decisions.
Actors:
1.
User – Reports the project
2.
Kickstarter team/staff – evaluates project
3. Kickstarter system –
external system that provides info about the project
Creation Date: October 18 2013
Version: v1.0
Person in Charge: Student
Flow of Events
Preconditions:
1.
The User must have an account in Kickstarter
Main Success Scenario:
1.
User logs in his/her account in Kickstarter.
2.
User with his/her account in Kickstarter starts viewing projects by other
people.
3.
System displays all projects and its respective status.
4.
User finds a project that which the user thinks may have violated some rules
and regulations.
5.
User clicks on Report Project button.
6.
User fills out necessary details.
7.
System picks up the request and notifies Kickstarter staff to check on it.
8.
Kickstarter staff evaluates project if it is going above rules or simply wrong judgment.
9. User waits for further
actions or decisions.
Alternative Sequences:
A4. User decides not to report
project
1. User does not select any
options available on the check box.
2. User closes checkbox.
Error Sequences:
E7. Project is already
successfully launched/funded.
7. Kickstarter staff will have
a different approach on the project.
8. Use case ends
E4. Project has been taken down
or banned.
4. Use case ends
PostConditons:
1.
A report for the Kickstarter staff has been created.
UI (User Interface)
Requirements:
- Account
Identification Summary
Title: Fund Project
Summary: Fund a Kickstarter project via online payment
Actors:
1.
User – Funds the project
2.
Kickstarter team/staff – Process data concerning pledge amounts
3. Kickstarter system –
external system that provides info about the project
4. Amazon payment system –
external system that process online payment
Creation Date: October 18 2013
Version: v1.0
Person in Charge: Student
Flow of Events
Preconditions:
1.
The User must
have an account in Kickstarter.
2.
The User must
have a valid credit card.
Main Success Scenario:
1.
User logs in his/her account in Kickstarter.
2.
User with his/her account in Kickstarter starts viewing projects by other
people.
3.
System displays all projects and its respective status.
4.
User finds a project that catches user’s attention.
5.
User clicks on Back This Project button.
6.
User inputs Dollar amount.
7.
User selects reward tier.
8.
User is satisfied by their choice and proceeds by clicking the Continue to
Amazon button.
9. Amazon requests account
information.
10. User inputs account
information.
11. User proceeds to logging
in.
12. User selects mode of
payment and which credit card to use.
13. User clicks Confirm to
continue.
14. User goes back to project
page
Alternative Sequences:
A5. User decides not to fund
the project.
1. User does not provide any
information on payment and reward tier.
2. Proceeds to step 14
A9. User does not have an account
in Amazon, thus creating one.
1. User selects 2nd
option in Amazon page.
2. User fills out necessary
information.
3. Proceeds to step 10
A14. User would like to cancel/
change pledge.
1. User selects Manage Your Pledge.
2. User inputs necessary
information.
3. Proceeds to step 14
Error Sequences:
E7. Project is already launched/funded.
7. Button for Backing a project
will not appear.
8. Use case ends.
PostConditons:
1.
A project in Kickstarter would be funded.
2.
User will be able to manage their pledge.
3.
User will receive notification about project status.
UI (User Interface)
Requirements:
- Account
Identification Summary
Title: Start a Project
Summary: Start a project for people to back.
Actors:
1.
User – Starts the project.
2.
Kickstarter Project Specialist – reviews project.
3. Kickstarter system –
external system that provides info about the project.
4. Amazon payment system –
external system that process online payment.
Creation Date: October 18 2013
Version: v1.0
Person in Charge: Student
Flow of Events
Preconditions:
1.
The User must
have an account in Kickstarter.
2.
The User must
have a valid credit card.
3.
The User must
have a verified account in Amazon.
Main Success Scenario:
1.
User logs in his/her account in Kickstarter.
2.
User clicks Start a Project.
3.
User fills out basic information.
4.
User fills out backer rewards.
Repeat step 4 until satisfied
with multiple reward tiers.
5.
User fills out more information.
6.
User fills out necessary information about online payments.
7.
Amazon Payments verifies account.
6.
User submits complete information.
7.
Kickstarter system notifies administrators.
8.
Kickstarter Project Specialist reviews project.
9. Kickstarter Project
Specialist approves project.
10. User launches Project.
Alternative Sequences:
A5. User decides not fill any
information yet.
1. User does not provide any information.
2. Proceeds to step 6
A9. Project Specialist
disapproves of project and requests change/editing.
1. Project Specialist informs
user of problems.
2. User applies changes to
better fit regulations.
3. Proceeds to step 8
Error Sequences:
E1. User is not eligible to
start a project in Kickstarer due to location.
1. Ends case
PostConditons:
1.
A new project in Kickstarter would appear.
UI (User Interface)
Requirements:
- Account
Friday, October 11, 2013
User Case Diagram
My 1st attempt at a User Base diagram, the website i used is Kickstarter.com. Kickstarter is a website where people fund other people's projects.
Friday, October 4, 2013
Questions
I
would like to tackle a few questions regarding Systems Analysis, certain
systems, design processes, interviews and answer it with my own opinions. The
first question asks about the technicality of a system analyst or how technical
a system analyst must be. Being technical usually involves one being adept or knowledgeable
at a specific subject, choosing practical methods over idealistic ones and use
of practical tools. For me a system analyst can be both technical and not. It
means that a system analyst should be technical but only to some extent but not
limited to.
A system analyst has a unique blend of technical knowledge and
other skills for it to become effective. Yes, they should be technical and
possess technical knowledge but heavy technical jobs should be handled by
programmers who are required to be technical throughout. The next question is about
how a system analyst is different from the I.T. crowd and how different skills
sets are required and what skills fit in both. The first common ground I can
think of between I.T. roles and a system analyst is their technical knowledge and
understanding of the digital world. Even as the I.T. role has a deeper
knowledge about technical issues a system analyst would not fall far behind. A
big difference between the I.T. role and System Analysis is the fact that I.T.
personnel interact directly to the system analyst while the system analyst
connects to different people; from users, to designers and even the decision
making higher ups. In short system analysts possess interpersonal people
skills, management skills, analytical skills and technical know-how. System analysts
are not only good behind a keyboard for they are the people who connect
different pieces of the organization to from a working system. Now to a
different topic; a topic regarding roles and pyramids. In a large organization
different roles are required and they are filled with people with the right
skill sets.The organizational Pyramid |
sources:
Friday, September 27, 2013
Systems Analysis is the study of a procedure or process to define its goal and purpose and create a system to achieve it in the most efficient way. Simply put, systems analysis is basically helping the decision maker into making his/her choice which would result in the most beneficial outcome. Systems Analysis would require one to be both technically capable whilst having a good inter personal people skills as they are required to interact with clients and the system itself. A system analyst researches solutions, finds problems, and bridges different gaps in
the modern technological world. A system analyst coordinates with businesses and organizations and tells them which hardware and software to purchase and how to make them work together. A system analyst is a critical thinker, as competition is tough and fierce and the stakes high they are required to be both adaptive and cunning for them to produce long term solutions. They may or may not be directly involved in the programming itself but they are familiar with a variety of programming languages. In a simple definition system analysts are people who connects things and make them work together in a smoother way to make the best possible outcome. Now that we have established the definition of systems analysis we may venture further into its role in the future. In the modern age things change rapidly, as Bill Gates quotes "People always fear change. People feared electricity when it was invented, didn't they? People feared coal, they feared gas-powered engines... There will always be ignorance, and ignorance leads to fear. But with time, people will come to accept their silicon masters." we should come to accept that progress would not wait for us, it will be either come along or be left behind. This is where I believe systems analysts fit in, in the future of modern technology they have the capacity to understand and make change. As things get too complicated and technical in the future they would adapt. This is why I believe that systems analysts would play a major role in the technologically advanced future where almost everything would be probably digitized. Since they are flexible they would learn and adapt whatever new computer or universal language required. Because a system analyst is linked to the organization's or businesses' ability to deliver products not only of higher quality but also cheaper and faster. As technology continues to progress systems analysts have the skill and capability to understand and combine these factors to achieve its goal. Systems analysts will have a major part in the futuristic grand scheme of things, if everything does become digitized they will have an advantage.
image from www.bankacademy.com |
Subscribe to:
Posts (Atom)