Inspirational Qoutes fOr yOu

If you don't like something, change it; if you can't change it, change the way you think about it.

- Mary Engelbreit

Saturday, January 31, 2009

Contradiction??_Act. No. 1b (SE)

Question:
Brooks says that adding people to a late project makes it even later (Brooks 1975). Some schedule estimation techniques seem to indicate that adding people to a project can shorten development time. Is this a contradiction? Why or why not?

Both statements are true, there is no contradiction at both parties because both are referring into a good result or techniques for everybody.

For me it’s not a contradiction to Brooks point of view because what Brook mean is a late project and late project is still late and can even result to be later if a team should add a person to it. There is nothing new or can change the status of a late project to an earlier one if we add new person. Adding a person means new adjustment and basically can never change the fact that the project is late. It’s definitely true that adding one will make it even more late because you need to orient the new person, as if the group should start at the very beginning. Its not appropriate if the team added a person and just let the person study the previous stages that the group undergone.

What was the second article mean is that in developing a project or starting a project would be a big help if the personnel who will develop it is many. The more the merrier, as what the old saying goes. It’s an expression of a project to be more effective if it has lots of idea or head that are working. Two heads is better than one, right? In most cases, developing a system would mostly preferred by group and it’s an advantage to a group who has a more personnel. Task could be divided evenly and just.

Buy a software package_Act. No.1a (SE)

Manny’s Manufacturing must decide whether to build or buy a software package to keep track of its inventory. Manny’s computer experts estimate that it will cost 325M dollars to buy the necessary programs. To build the programs in-house, programmers will cost 5,000 dollars each per month. What factors should Manny consider in making his decision? When is it better to build? To buy?

Well as far as I understand in Manny’s dilemma, it would be great if he will buy the software. Lets just say that it cost more compare to the program to be built in-house, but how long would it take completing the program??. Building an in-house program would consume a big span of time. In the end, buying or building it would be of equal amount I guess.


The only different of the two is that buying the software would mean lending so much money quickly but the advantage of it is that Manny would easily use the inventory system for his company. That would give Manny the assurance of his company’s items. While building the program in-house would cause him so much time waiting for it to be completed which would waste his time were in fact, the cost is the same.


In the business world, you need to be business minded person. You should also consider the benefits it would bring into your company in spite of the cost. Manny should not only consider the money but the persons who are working on his company. He should offer the best and most effective way for them to have a result that is worth satisfying.


Nowadays, as we observe in all aspect of life especially when it comes to business you should be competitive. Big business should have an edge in everything they are doing or producing. Why not Manny start it first inside his company? That would be a better idea.

Friday, January 30, 2009

Complete Use Case Diagram of USEP Enrollment System (Assignment 5)


Complete Use Case Diagram of USEP Enrollment System

As you can see, compare to my last assignment of Use Case Diagram (Assign. 4) you can see in the diagram above some operations or conditions being added so that a particular system works effectively and efficiently if it involves some methods for certain situation that may occur as the process goes along.

Monday, January 12, 2009

Use Case Diagram of USEP Enrollment System [Assignment 4]


Figure: USEP Enrollment System Diagram

As you can see in this diagram (though its kinda tricky) but it only shows that creating a use case diagram is not that easy. SEE the details below to further understand it:

a.) Red Arrows/Lines is for the processes that a Student should take into consideration.
b.) Yellow Circles are for the arrangement of the process, what process should be taken first and so on..
c.) Blue represents here the role of the each actor(s) in the diagram.
d.) Pink/Violet lines is representing is connecting the yellow circles.

1.) Local Fees = includes the LC, Headlight and OCSC. The treasurer then issues a receipt after the enrollee pays his/her local fees.
2.) Advising = evaluation of grades and subjects which would be given by the adviser of each year level and after doing so issues a PRF and signed.
3.) Encoding here is to encode all the data that was approved by the adviser. The encoder issues a COR afterward.
4.) Cashier = where financial transactions esp. tuition fees are being paid. after paying his/her bill cashier now issues a receipt.
5.) Book keepers role here is optional for student, book keeper ony validates those students who have scholarships.
6.) Registrar= one who register a student that he/she is officially enrolled and has completed all the necessary processes required.
7.) Library= the librarian would be the one to validate the e-lib.
8.) and lastly, after passing all the following processes required the enrollee now is Officially Enrolled.