Skip to main content

#TI2011 #ChapterFive

2 min read

Chapter Five

Review of the 5th chapter

I hope this chapter is as cool as I think, let’s start and you’ll know my answer in the next lines of how amazing it was…

Yep, it was awesome, let’s start step by step what impact the chapter created in me.

In the intellectual phases, we have three, the first one is discovery that is characterized of converting uncertainty to certainty through investigation, such as knowing what the user, customer, client want and creating user interfaces, the second phase is the invention like the discovery phase only that things that couldn’t be certain in discovery they are at invention and finally the third, implementation it focused on realizing what is certain by the other two phases.

At each stage of implementation, the group task release functional product in each stage delivery is provide several important benefits, like critical functionality, reduced risks, evident problems, reduced status-reporting, more options, reduces possibility of error, balances flexibility and efficiency.

The disadvantage of each stage is that everything is repeated so each action for each stage cost more, but is so minimum that the cost is worth it against doing it all again because there was a mistake at downstream that will cost more than doing it by each stage.

In this chapter I learned that completing stages is better than doing each part alone, that would be all for now, until the next one.


#TI2011 #ChapterFour

2 min read

Chapter Four

Review of the 4th chapter

Normally people are not used to plan because they think is a waste of time and make stress knowing how much they must do to make the project run, but normally is because they don’t know how to plan.

Last post I didn’t explain in short words what was upstream and downstream but here we go, upstream is the early part of the project, requirements, development and architecture and downstream is the later part of the project that consist of construction and system testing so is much cheaper make a change or fix a defect in the upstream than the downstream.

The thing is, we must plan because the average project spends 80 percent of the time on unplanned rework that is fixing or changing things that wouldn’t have happened if we had planned at the beginning.

Let start with specific features of a well-planned project. First we got a Software Development Plan this maps the course for the project, second the project estimates that leads to budgeting, staffing and scheduling the project, third revised estimates, check if what is going to be spent and how much the project will earn, after that is a quality assurance plan that will not succumb to a costly project and will be at perfect conditions, finally a staged delivery plan how the project will be constructed.

The first part of the project is essential because determines if the project is a “go/no go” if it’s correctly planned, the project will show you if is convenient per time and develop of the group task or not, so this part is very important that the client, user, customer is present so he can validate every point or any change before the project starts and check if the time/cost he will pay is worth the possible outcome.

In this chapter I learned that develop a plan and be aware of different situations that could be against the programmer (cost, time, impossible projects) is essential to make a quality software, that would be all for now, until the next one.


#TI2011 #ChapterThree

2 min read

Chapter Three

Review of the 3rd chapter

Survival concepts this chapter lead you to make your software successful, this is about using effective development processes to make effective Software, I’m sure you were expecting that.

So, first what is a process, the book throw us a lot of meanings but the one that got my attention is developing a systematic plan in early stages of the project that includes a test plan, review plan, and defect tracking plan, because this “extras” are essential to know if you are going good or something is going terrible bad so you can change it before you are at a stage that is very expensive making changes.

Normally people don’t think that a process is a good way of working they think that hiring people and throw them to do what they are the best is the way Software magically appear, but they are wrong even the best programmers or in our case engineers in computer science we have a process to follow so Software can “magically appear”.

The reason we spend time at the process stage is to AVOID mistakes not to CORRECT mistakes, that simple. Change control, customer want changes and those changes without a process stage expand budget and schedule. Quality assurance, the process to eliminate defects are very important so important that if the project have many mistakes in the testing stage become a chaos because it have interminable fixtures. Uncontrolled revisions, defects are discovered because no one planned and the project deviates from its final purpose. Defects tracking, when defects aren’t fixed and the software is released. System integration, the components where divided and they are integrated until the end of the project so it takes time to align them or they could be incompatible. Automated source code control, developers can lose work or overwrite code they have and lose parts that were essential. Finally scheduling, projects that are behind schedule, developers are asked to re-estimate work. 

In this chapter I learned that make process and be very organized is essential to make a quality software, that would be all for now, until the next one.


#TI2011 #ChapterTwo

1 min read

Chapter Two

Review of the 2nd Chapter

The Software Project Survival Test is a test to know if the project you are on the way to develop is going to succeed or be a long task to develop it correctly or is definitely going to fail.

I can’t review this because is a guideline to know how will be the process of developing any project, is a way to know and question yourself about what are you going to do with the project you will be working on. The questionnaire is about things that we read on chapter one so this represents if the project is well defined, it has an available and good group task, communication with the client, and many other things.

The interpretation of the test tells us if the software is Outstanding, this means is virtually guaranteed of success, Excellent, performing much better than the average, Good, better than average level, Fair, it will affect the survival rights and needs from chapter one and finally at risk problems in all areas and should be checked again.


#TI2011 #ChapterOne

2 min read

Chapter One

Review of the 1st chapter

Users and clients usually want Software that is cheap and fast to develop but I have never seen a quality one that is cheap and fast so our buyers must know how we survive developing and creating their amazing ideas,

In software project survival, you must recognize the essential needs that are simple like the project isn’t canceled, team isn’t fired, adequate physical working conditions, everything that is basic to start a project which satisfy yourself and your group task at maximum performance, then you have the safety needs which exist to meet personal promises for schedule and functionality. After needs you have social contact, belongingness and love that is the fact of having a healthy and good communications with the group task. Now you have complete needs and you have a good relation with your team now is your self-esteem what matters the objective is a productive feeling, that you are important to the develop of the project and you are contributing to it and finally the self-actualization that is a professional development that is the fact of knowing what is happening in your environment. 

The survival rights are things that the client and the developer must agree so the project can be a civilize work, both must know the project and objectives, access to people to make decisions of functionality, work each phase of the project in a productive environment, involvement of the client so everything goes well.

Very interesting chapter I learn many things about developing projects and the things we need to do to make a successful one, until the next one.


#TI2011 - Sign the page one

1 min read

Hey, what's up, here is the first post for about page one


#TC201 #Topic15 What is the metaobject protocol?

1 min read

metaobject protocol (MOP) provides the vocabulary to access and manipulate the structure and behavior of objects. Typical functions of a metaobject protocol include:

  • Creating and deleting new classes
  • Creating new methods and properties
  • Changing the class structure so that classes inherit from different classes
  • Generating or modifying the code that defines the methods for the class

Source: Wikipedia.


#WSQ11 #Java #TC201 Library Assignment Programming Fun

1 min read

The libraries of SmallTownX need a new electronic rental system, and it is up to you to build it. SmallTownX has two libraries. Each library offers many books to rent. Customers can print the list of available books, borrow, and return books.



We provide two classes, Book and Library, that provide the functionality for the book database. You must implement the missing methods to make these classes work. 

The first part of the problem that is the implementation of Book was easy, we only put what they asked us to put, filling the methods is easy if you already have the other WSQ, the hard part is when is the turn of the Library at first we have to make the address of the library, that's simple, then we have to make an ArrayList where all the books will be, that's the hard part, then we have to check the hours the both libraries are available, that's very simple, then borrow and return books that's the hard part but when you get it is simple.

I won't post pictures because I'm lazy but here's the code 




#WSQ10 #Java #TC201 - College Advice

2 min read

I like this from Joel Sposky, "If you enjoy programming computers, count your blessings: you are in a very fortunate minority of people who can make a great living doing work they enjoy. Most people aren't so lucky. The very idea that you can "love your job" is a modern concept. Work is supposed to be something unpleasant you do to get money to do the things you actually like doing".


  • Learn how to write before graduating

This is a great advice because to express your ideas you need the abilities to transmit them, and writting and SPEAKING, he miss that, are a very usefull.

  • Learn C before graduating.

I asked many programmers what I must learn before I graduate and actually all of them answer me the same, learn C, is the base for all, so I'll take this advice. 

  • Learn microeconomics before graduating.

My dad had always said to me that the difference between a common CS engineer and me can be the way I present myself and the business stuff I know, so actually this advice is already done 

  • Don't blow off non-CS classes just because they're boring.

I'm trying myself so hard to keep at least a 3.0 in my GPA, but I have to admit that is hard but I'll do my best.

  • Take programming-intensive courses.

I already take intensive programming courses, they are awesome, but the things that I have learnt I kind of forgot them because the practice makes the master, so actually the adivce is keep programming so you can be awesome at what you do

  • Stop worrying about all the jobs going to India.

I heard about India and how cool they are at my area but the thing is that if you can develop a great idea that no one have, that's the key of success, be good at something and create awesome things that help humanity

  • No matter what you do, get a good summer internship.

I'll take this advice unless I develop an idea that changes the world