What Major is Right For Me?

WHAT MAJOR IS RIGHT FOR YOU? created with QuizFarm.com

You scored as Accounting/Finance/Marketing You should strongly consider majoring (or minoring) in Accounting, Finance, Economics, Marketing, or related majors (e.g., Computer/Management Information Systems (CIS or MIS), Entrepreneurship, International Business, Operations Management, Public Administration, Real Estate, Risk Management, Sports Management). It is possible that the best major for you is your 2nd, 3rd, or even 5th listed category, so be sure to consider ALL majors in your OTHER high scoring categories (below). You may score high in a category you didnt think you would--it is possible that a great major for you is something you once dismissed as not for you. The right major for you will be something 1) you love and enjoy and 2) are really great at it. Consider adding a minor or double majoring to make yourself standout and to combine your interests. Please post your results in your myspace/blog/journal. Accounting/Finance/Marketing 100% Psychology/Sociology 88% Nursing/AthleticTraining/Health 75% Education/Counseling 69% Biology/Chemistry/Geology 69% Visual&PerformingArts 69% Physics/Engineering/Computer 63% French/Spanish/OtherLanguage 63% HR/BusinessManagement 56% Mathematics/Statistics 50% PoliticalScience/Philosophy 44% Religion/Theology 44% English/Journalism/Comm 31% History/Anthropology/LiberalArts 19%

Mackygrupo Progress Report 10

Mar24-28

Things we have accomplished: Jerick prototype Daryl installer and exe Tina updated user manual Macky Lalaine revised report layouts documentation - interview summary, interview questions, revised class diagrams, description final presentation slides

Our next week goals are: vacation! CS 130 Exam

Our most important concerns/issues/questions are:

We learned: Jerick py-bcript, more about the project Daryl py2exe, NSIS Tina more about revising documentation Macky Lalaine more about documentation

Mackygrupo Progress Report 9

Mar17-23

Things we have accomplished: Jerick prototype, started connecting the db Daryl db Tina updated user manual Macky Lalaine meeting with client

Our next week goals are: Final Presentation Finalize Project - prototype and database Finalize Documentation

Our most important concerns/issues/questions are: Additional features specified by client - needs to be discussed prototype features and layout revision of logical database design

We learned: Jerick different ways to print using python. Daryl pysqlite Tina more about revising documentation Macky Lalaine sqlite features of glade more about the database

Mackygrupo Progress Report 9

Mar17-23

Things we have accomplished: Jerick prototype, started connecting the db Daryl db Tina updated user manual Macky Lalaine meeting with client

Our next week goals are: Final Presentation Finalize Project - prototype and database Finalize Documentation

Our most important concerns/issues/questions are: Additional features specified by client - needs to be discussed prototype features and layout revision of logical database design

We learned: Jerick different ways to print using python. Daryl pysqlite Tina more about revising documentation Macky Lalaine sqlite features of glade more about the database

Mackygrupo Progress Report 8

Mar10-Mar16

Things we have accomplished: Jerick prototype Daryl db Tina updated user manual Macky Lalaine

Our next week goals are: Prototype database implementation

Our most important concerns/issues/questions are: database design revisions prototype design

We learned: Jerick more about gtk Daryl more about pysqlite Tina revising documentation Macky Lalaine more about SQLite using SQLite manager

Mackygrupo Progress Report 7

Mar3-Mar9

Things we have accomplished: Jerick updated prototype Daryl db Tina updated user manual Macky Lalaine

Our next week goals are: Prototype Database Implementation

Our most important concerns/issues/questions are: Using pysqlite and SQLite instead of mysql prototype design

We learned: Jerick features of sqlite Daryl SQLite, pysqlite Tina documentation has to keep up with a prototype's flexibility Macky Lalaine SQLite

Mackygrupo Progress Report 7

Mar3-Mar9

Things we have accomplished: Jerick updated prototype Daryl db Tina updated user manual Macky Lalaine

Our next week goals are: Prototype Database Implementation

Our most important concerns/issues/questions are: Using pysqlite and SQLite instead of mysql prototype design

We learned: Jerick features of sqlite Daryl SQLite, pysqlite Tina documentation has to keep up with a prototype's flexibility Macky Lalaine SQLite

Mackygrupo Progress Report 6

Feb 25-Mar2

Things we have accomplished: Jerick updated prototype Daryl updated screen prototype Tina updated user manual Macky Lalaine Poster for CS Symposium meeting with client

Our next week goals are: Final Prototype Database Implementation

Our most important concerns/issues/questions are: prototype design

We learned: Jerick other useful python modules. Daryl more about gtk, pygtk, python, and various python modules Tina keeping documentation up-to-date Macky Lalaine how to use Adobe Photoshop formulas to be used in the project

Mackygrupo Progress Report 6

Feb 25-Mar2

Things we have accomplished: Jerick updated prototype Daryl updated screen prototype Tina updated user manual Macky Lalaine Poster for CS Symposium meeting with client

Our next week goals are: Final Prototype Database Implementation

Our most important concerns/issues/questions are: prototype design

We learned: Jerick other useful python modules. Daryl more about gtk, pygtk, python, and various python modules Tina keeping documentation up-to-date Macky Lalaine how to use Adobe Photoshop formulas to be used in the project

Mackygrupo Progress Report 5

PROGRESS REPORT

Feb 18-24

Things we have accomplished: Jerick Updated screen prototype Daryl Updated screen prototype Tina updated user manual Macky database implementation Lalaine database implementation sample data

Our next week goals are: Final Prototype Database Implementation Project Poster

Our most important concerns/issues/questions are:

We learned: Jerick more about gtk Daryl more about python and gtk Tina proofreading documentation Macky Using MySQL Query Browser Lalaine using SQLyog enterprise using MySQL Query Browser

Mackygrupo Progress Report 4

Feb 11-17

Things we have accomplished: Jerick Prototype Daryl Tina Macky Lalaine Report Layouts

Our next week goals are: Final Prototype User Manual Report Layouts Database Implementation

Our most important concerns/issues/questions are:

We learned: Jerick The use of Matplotlib, a plotting library for python. How to draw a pie chart using Matplotlib. More on Tepache, PyGTK, Python. Daryl Tina Macky Lalaine

GP’s Progress Report 8

This week we have accomplished

->Integration of all the codes made

• Beth Mercado: Tested the program for applicant functionalities
• Rona Tadlas: Tested the program for scholar functionalities
• Perla Loro: Tested the program for administrator’s functionalities
• KC Ferre: Tested the error cases of the program,updated and finalized all documentations

Our next week goals:

• Debugging of codes and preparation for the final presentation

Our most important concerns/issue:

· There are lots of errors encountered when we integrated our individual codes

We learned:

• Beth Mercado: Testing of the project by other people is really important and as well as the relation of all documentation with the final project. Teamwork is really needed in every group activity.
• Rona Tadlas: Teamwork and time management are important.
• Perla Loro: Teamwork and time management are very vital in creating a project
• KC Ferre: Integration of all we made in the project must really be given enough time because there were some inconsistencies that were not avoided

GP’s Progress Report 7

This week we have accomplished

• Beth Mercado: Connected the applicant functionalities to the database
• Rona Tadlas: Connected the scholar functionalities to the database
• Perla Loro: Connected most of the admin functionalities to the database, tested the program
• KC Ferre: Helped in connecting the admin functionalities to the database, made error checking codes, added confirmation messages for deletion

Our next week goals:

• Finalize the connection to the database, integration of all the codes into one final code and test the program if it’s functioning correctly

Our most important concerns/issue:

· MySQL queries and inconsistency of variables

We learned:

• Beth Mercado: Integration of our codes is very erroneous
• Rona Tadlas: Software testing is important
• Perla Loro: Integration needs extra carefulness
• KC Ferre: It’s hard to work on other’s codes and comments would really help understanding those codes that’s why it’s more advisable to work together for easier understanding of codes

GP’s Progress Report 6

This week we have accomplished

• Beth Mercado: Finalized the project’s prototypes
• Rona Tadlas: Finalized the project’s prototypes
• Perla Loro: Connected the log-in interface to the database
• KC Ferre: Started connecting the viewing functionality of administrator to the database

Our next week goals:

• Continue connecting the user interface to the database

Our most important concerns/issue:

· It’s been hard connecting to the database when the prototypes aren’t yet final.

We learned:

• Beth Mercado: MySQL, PHP
• Rona Tadlas: My SQL, PHP
• Perla Loro: MySQL, PHP
• KC Ferre: MySQL, PHP

GP’s Progress Report 5

This week we have accomplished:

• Beth Mercado: Make necessary changes in the project’s prototypes
• Rona Tadlas: Make ‘create table’ queries
• Perla Loro: Encrypted passwords using sha1 and handled sessions
• KC Ferre: Make ‘insert table’ queries with all the sufficient sample data

Our next week goals:

• Connect the database to the user interface

Our most important concerns/issue:

· There are some problems regarding foreign keys in our queries

We learned:

• Beth Mercado: how to connect database to the project
• Rona Tadlas: MySQL queries
• Perla Loro: use sha1 and make sessions
• KC Ferre: one cannot insert data in some tables if it refers to a non-existent foreign key of another table; and to validly insert data, one should consider the types of variables, constraints, etc.

Problem at Day1 Solved!

Found out we were throwing in and getting wrong stuff with the Servlet. On to integration! =)

Day One of Working With RPC's...

and we weren't blessed with a beginner's luck.

The Orgster team decided to have an overnight session to work on the deadline for this week, and that is to be able to integrate the user interface with the database. Rj worked on the polishing of the user interface while Cez and Mei Ann explored the remote procedure calls (RPCs) in GWT. Malen reconstructed the database queries and sample data. The tutorials at the GWT developer website guided Cez and Mei Ann in making this "bridge" between client (the one using the interface) and the server (the one that executes the requests from the user). But we always get an error that the server class was not instantiated. Malen tried to build the project that Cez and Mei Ann are having errors with, using Eclipse but she gets a NullPointerException.

We need to solve this problem asap. We need to read more about remote procedure calls to be able to implement it because we're still clueless about it. Deadline is on Friday.. =s

ORGSTER PROGRESS REPORT[2]

This week we have accomplished:

• RJ Raymundo: Redesign prototypes for Orgster's log in page, user home page, calendar and organization page
• Cez Castro: Prototypes for messaging and bulletin board
• Anj Duran: Prototypes for messaging and bulletin board
• Malen Bacay: Orgster Database
• Mei Ubina: Orgster Database
  

Our next week goals:

• Finalize Prototypes
• Connect database and user interface
  

Our most important concerns/issue:

• Database and user interface connection
  

We Learned:

• RJ Raymundo: HTML, CSS, and advance interface design
• Cez Castro: GWT
• Anj Duran: GWT
• Malen Bacay: MySQL
• Mei Ubina: MySQL
  

GP’s Progress Report 4

This week we have accomplished:

• Beth Mercado: Improved our project’s prototypes(minimized the no. of pages) and helped finalizing the tables
• Rona Tadlas: Improved our project’s prototypes(minimized the no. of pages) and helped finalizing the tables
• Perla Loro: Final draft of the normalized tables
• KC Ferre: Final draft of the user manual and helped in finalizing the tables

Our next week goals:

• Create the database and insert sample data

Our most important concerns/issue:

· Not sure if the normalized tables are really correct and final

We learned:

• Beth Mercado: changes really happen along the duration of the project.
• Rona Tadlas: modifications and changes cannot be avoided
• Perla Loro: some tables that we created can be combined into one
• KC Ferre: the user manual, with the screenshots, cannot really be finalized unless the prototypes are already final

Mackgrupo Progress Report 3

Feb 4-10, 2008

Things we have accomplished:

Jerick

• Updated the screen prototypes.
  

Daryl

• Updated the screen prototypes.
  

Tina

• Updated user manual
  

Macky

• Updated the Normalization of tables
  

Lalaine

• Updated Original Customer Table and Final Report
• Updated Normalized Tables
• Asked client for some clarifications about some terms.

Our next week goals are:

• Final Prototype
• User Manual
• TNF Normalized Tables (Table Format) with sample data
• Sample forms

Our most important concerns/issues/questions are:

• Mr. Uy has just returned to Isabela and will not be able to come back until March.
  
• We still have some questions to ask him.

We learned:

Jerick

• More about pyGTK, glade, Tepache, and GTK+ themes (for screen prototypes)

Daryl

• More about pyGTK, glade, Tepache, and GTK+ themes (for screen prototypes)
  

Tina

• Paying attention to small details in the application that a user may have problems with
  

Macky

• Learned how to normalize tables
  

Lalaine

• more about the system.

Mackygrupo Progress Report 2

January 28, 2008 to February 3, 2008

Things we have accomplished:

Jerick

• Redesigned the user interface.
  

Daryl

• Theme for the user interface.
  

Tina

• First draft of the user manual
  

Macky

• Normalizing Tables
  

Lalaine

• Normalizing Tables

Our next week goals are:

• Prototype
• User Manual
• TNF Normalized Tables (Table Format)

Our most important concerns/issues/questions are:

• Did we do a good job on normalizing the tables?

We learned:

Jerick

• The use of tepache, a code sketcher for python.
  

Daryl

• GTK themes, Tepache
  

Tina

• How to write a beginner-friendly user manual
  

Macky

• How to correctly normalize tables.
  

Lalaine

• How to normalize tables.

GP’s Progress Report 3

This week we have accomplished:

• Beth Mercado: Modified our project’s prototypes
• Rona Tadlas Modified our project’s prototypes
• Perla Loro: Second draft of the normalized tables
• KC Ferre: First draft of the user manual, updated Use Case Diagram and Analysis Class Diagram

Our next week goals:

• Finalize the normalized tables

Our most important concerns/issue:

· How to improve the user interface of the project

We learned:

• Beth Mercado: Basics of php
• Rona Tadlas: Basics of php
• Perla Loro: it's easier to normalize if you would use the warrie orr notation
• KC Ferre: use umlet for easier making of diagrams; and one needs to be very detailed in making a user manual and should consider that the intended reader has no knowledge of how to use the system

Mentorsplus Online Description

Mentorsplus offers center based tutorial services which range from intensive Math, Science, and English sessions to regular three times a week session covering all major subjects. Services are offered to all students from elementary to college. The main approach of the center is the tapping and the enhancement of the basic skills and fundamentals of every subject matter for experience would tell that the basic allows learners to gauge very well various problems, questions, exercises. The basic approach allows students to creatively think of strategies in getting the right answers.

Mr. Aldo Garcia, the director and owner of Mentorsplus wants to improve the system implemented in the center. With this, Mentorsplus Online is conceptualized with the Jjamppong group.

Mentorsplus Online is a website that would inform the user about the center: its history, services offered, events held and announcements. Students may post their comments or feedbacks about the tutorial center.

Also, this would help the owner to keep track the operations of Mentorsplus. That is, he would be able to maintain and manage the profile of the students, as well as the tutors.

Girl Power Progress Report 2

This week we have accomplished:

• Beth Mercado: Modified the prototypes for OSAS log-in and users’ main pages
• Rona Tadlas: Improved the UP logo and header of all the pages and make the sizes of the horizontal and vertical bars as fix as possible when the user browse through different pages
• Perla Loro: First draft of the normalized tables
• KC Ferre: Updated the RTM

Our next week goals:

• Continue designing the prototypes
• Check the normalized tables

Our most important concerns/issue:

• How to normalize tables correctly

We learned:

• Beth Mercado: how to use dreamweaver for easier designing of prototypes
• Rona Tadlas:
• Perla Loro: we can also use primary keys that are not by default included in the attributes of a table
• KC Ferre: rtm secarios should include all the expected scenarios and update or rtm is important to know which of the prototypes are not yet done
  

mEeTinGs!

THE FIRST MEETING- WE HAVE A CLIENT!!!

December 4, 2007. Jjamppong, our group marked our first meeting. It happened at the Eng'g Library II, Discussion Room. Just today, we finally get to have a confirmation about a demand from one client, Mentors Plus Tutorial Center. Basically, Mr. Aldo Garcia, the owner of the said tutorial center wanted to alter the way they store and manage their records, which is by manually stacking these documents in a filing cabinet. Mr. Garcia wanted to have an on-line record management program that would simplify his work on this matter. Jenny, a group member, upon having a talk with Mr. Garcia, relayed to everybody in Jjamppong some details on the dos and donts, the musts and the nots and a little overview of the said project. Our group evaluates the said offer by considering the length of time and cost that this one semester would limit to us. We also tackle about some matters such as what programming language to use for on-line deployment of the project, possible flaws we may encounter in the future and when will be our formal meeting with the client if ever we decided to grab the offer. We still need to talk our schedules out, the groups' and also the client's, for us to finally set the date. This is actually how we ended the meeting.

THE SECOND MEETING PART 1- CAN WE DO IT? YES OF COURSE!

December 6, 2007. A short yet packed meeting. Since we still have time (before our next class start) we decided to have a short chat about our project. We ended up studying the project at the 2^nd Floor Lobby of Eng'g Library II. We set things straight, just for the record. Are we going to do it? Can we do it? JT, one of the members says that it is not that hard to implement a database, however the project as of now is too simple to comply with the cs 192 requirements. Also other members said that they have a slight background in making a simple database. With this, the group finally made a deal to give this project a chance. We would just ask the owner what more does he wanted to include in the project. We decided, for now, to use JavaScript and mySQL, if ever, for the coding part. We supposed to meet the client tomorrow.

SECOND MEETING PART1.1

December 6, 2007. Mood swings, Decision left dangling. Later on the day there is a bit change on the schedule of the formal meeting, and it's NATURAL! We decided not to push through the activity tomorrow since not everyone would be available to come. We realized that as much as possible, everyone must be there before we start on agreeing on some specifications that will be given by the client. Everyone must be involve in the negotiation. Ja, Jap and Ryan, wouldn't be available in Saturdays and JT in Mondays, because of these the meeting was moved to Tuesday, December 11. But again it is tentative.

THIRD MEETING- MAKING THE FIRST STEP.

December 13, 2007. The third meeting, Just got excited. Today is just a short meeting. Even though we haven't meet the client we decided to make a sort of “Use Case Diagram” for the current specifications he gave. Perhaps, we are just being so excited about the making of the diagram for we are carried away by the Bulilit Liga stuff. Anyway, we talked about the main use cases needed for the project while having our breakfast at the new CS canteen before moving to where else? The Engineering Library II, Discussion Room. As of now, we have the basic, or should we say, the very basic picture of the project. We have in our draft of the diagram are the following: the Add, Edit and View functions, The Log-In Interface for security and the two actors, the administrator and the staff. However, again this is temporary for big changes sure awaits us when we finally meet Mr. Garcia.

FOURTH MEETING- WELCOME 2008. THIS IS THE DAY!

January 3, 2008. Vacation is over, we have to move on. We are quite left back by the flow of events of the past year but we are and we must catch up. It is FINAL. We have to have a personal meeting with the client for formality sake and also for elaboration of certain aspects today. But before going to that, Jjamppong group had organize the things we are going to present with the client. We made a short summary of the things the clients wanted to have in the project, some suggestions and questions of ours. We are going to meet in the afternoon and go to mentors plus center as a group to have a face-to-face with Mr. Garcia. A few touches and were set. Gladly, we don't have classes today so we have the whole day to tackle matters.

FIFTH MEETING- JUST MADE OUR FIRST STEP.

January 3, 2008. We rode the jeepney to Katipunan where we are about to meet our client. THIS IS REALLY IS IT. The day everyone has been waiting for, our first personal encounter with the owner of Mentorsplus Center, Mr. Aldo Garcia. The center is located at Golden Crescent Mansion, R. Alvero Street, Katipunan. Sir Aldo made some points on what the functions in the Mentorsplus website are such as adding student and adviser records, updating the finances, and tracking the attendance of the students. We had some arguments which specifications may and may not be done. Forum is requested but due to time constraints, we refused to include it the specifications. After the meeting, we planned to meet again to talk about the work distribution and other stuffs concerning the project.

Jjamppong is here!!!

Meet the jjamppongers!

Jay Andrae Salvador (Jap)
John Anthony Bautista (JA)
Ryan Balane (Rye)
Jennifer Cunanan (Jenny)
Jeremiah Tristan Balugay (JT)

Project: Mentorsplus Online
Client: Mr. Aldo Garcia

Mackygrupo Progress Report (1)

Things we have accomplished:

Jerick
* Use Case Specification
* Screen Prototypes

Daryl
* Class Diagram
* UCD

Tina
* Use Case Specification
* RTM

Macky


Lalaine
* Use Case Specification
* Use Case Diagram
* RTM
* Gathering of Sample Data from Client

Our next week goals are:
*Normalized tables
*User’s Manual
*Completion of screen prototypes

Our most important concerns/issues/questions are:
*Database Normalization


We learned:

Jerick
* What is Glade, how to use it and how easy it is to create user interfaces with it. :)
* How to use PyGTK as bindings for Glade in Python
* How to program in Python

Daryl
*How to use python and glade in making applications with user interfaces
*How important class diagrams are
*How to use UMLet 8.0 and Umbrello

Tina

Macky

Lalaine
*How to use UMLET 8.0
*More on how the database should work (as specified by the client and after doing the Use Case Specifications)
*The existence of GTK (",)

ORGSTER PROGRESS REPORT[1]

This week we have accomplished:

• Ryan Joseph Raymundo: Orgster Screen Prototypes for Logging in and Calendar
• Ma. Elena Bacay: Database Normalization, Analysis Class Diagram
• Maria Cecille Castro: Use Case Specifications
• Angelica Duran: Use Case Specifications
• Mei Ann Ubina: RTM, Analysis Class Diagram

Our next week goals are:

• Orgster Screen prototypes for maintenance of organization database
• Finalize database normalization
  

Our most important concerns/ issues / questions are:

• Concern: Database Normalization
  

We learned:

• Ma. Elena Bacay:
  "I learned FDs and normalization forms. I had difficulty understanding FDs at the first time. Good thing there are examples online. It isn't easy to normalize, I realized one has to know the project data really well, like which relates to what, which ones can be derived and so on."
• Maria Cecille Castro:
  "I learned design model components and logical database design (FDs and normalization forms)."
• Angelica Duran:
  "I learned logical database design. And I also learned that use case specifications must be very precise."
• Ryan Joseph Raymundo:
  "I learned GWT, design model components and how to represent data in forms of tables."
• Mei Ann Ubina:
  "I learned logical database design, design model components and the importance of RTM, it must be definite."

GP report on "UP ONLINE SCHOLARSHIP APPLICATION DATABASE SYSTEM"

Yesterday, January 16, 2008 at around 11 am, our group (Girl Power) reported the recent development of our project(UP OSADS). We presented the prototypes of the system with an integrated php codes already. Here are the comments of Ma'am Solamo and the revisions she have suggested.

Login - Make the textfield name visible.
In updating the status of the applicant - instead of displaying a list of all the applicants with a drop down menu for "Approved or Disapproved", why not just search the applicant to be updated using his/her student number instead of having a long list of applicant on the screen.
Password - should not be used as a primary key because it changes from time to time.
Username - as a primary key is also not recommended, numbers are preferred.
Email add - can be used as a primary key
Grade - be made into GPA
Primary keys are unique, and cannot be a null value.

** Finalize the normalization to be emailed by monday -- perl
** Develop all interfaces, check and update with the rtm
--start with the must haves scenarios
update with rtm---kc
interfaces -- beth and rona