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.