Steps in Buying a House

Buying a Home The homebuying process can seem complicated, but if you take things step-by-step, you will soon be holding the keys to your own home!Nine steps to buying a home:

1.Figure out how much you can afford

2.Know your rights

3.Shop for a loan

4.Learn about homebuying programs

5.Shop for a home

6.Make an offer

7.Get a home inspection

8.Shop for homeowners insurance

9.Sign papers--------*****************************************************

--------

Step 1: Figure out how much you can affordWhat you can afford depends on your income, credit rating, current monthly expenses, downpayment and the interest rate. The calculators below can help, but it is best to visit a lender to find out for sure.A housing counselor can help you figure out how to manage and pay off your debt, and start saving for that downpayment!

Step 2: Know your rightsStep

3: Shop for a loanSave money by doing your homework. Talk to several lenders, compare costs and interest rates, negotiate to get a better deal. Consider getting pre-approved for a loan.

Step4: Learn about homebuying programs

Step 5: Shop for a home

Step 6: Make an offerDiscuss the process with your real estate agent. If the seller counters your offer, you may need to negotiate until you both agree to the terms of the sale.

Step 7: Get a home inspectionMake your offer contingent on a home inspection. An inspection will tell you about the condition of the home, and can help you avoid buying a home that needs major repairs.

Step 8: Shop for homeowners insuranceLenders require that you have homeowners insurance. Be sure to shop around.

Step 9: Sign papersYou're finally ready to go to "settlement" or "closing." Be sure to read everything before you sign!

USE CASE

Use Case: “Search for the books”
Short Description: “The Students are able to borrow a book in the library”
Actor: “Students”
Requirements: “Each Student should have an ID”
Pre Condition: “Each ID of Student should already validated”
Post Condition: “The Students are able to borrow a book”
Main Flow: “Each Student put their name, signature, code of the book and the date to a specified record book”
Alternate Flow: “Your ID was not validate”
Exceptions Flow: “No network connection”

Exercise 2: Conduct User Training

What is Risk?

What is Disaster Prevention and Mitigation? Risk is the probability that a hazard will turn into a disaster. Vulnerability and hazards are not dangerous, takenseparately. But if they come together, they become a risk or, in other words, the probability that a disaster willhappen.Nevertheless, risks can be reduced or managed. If we are careful about how we treat the environment, and if we areaware of our weaknesses and vulnerabilities to existing hazards, then we can take measures to make sure thathazards do not turn into disasters.

5 software risks:

a.)Staff Turnover: This kind of software can affect the success or failure of a project since in this situation. the working staff leave before the project is finished, so we can just imagine the scenario when there is staff turnover, so the whole project and the management will be put in "hot water".

b.) The project itself: This kind of software risks include inadequate configuration control, cost overruns and poor quality. Poor quality means the software either does not work very well, or it fails in operation repeatedly. So this is problem once it is encounter.

c.) Commercial software risks: A finished project may have lower user satisfaction. Lower user satisfaction means the product has low quality, functions inadequately, and has complex structures. Users are also displeased by excessive utilization of disk space or other hardware components requirements by the software.

d.) Hardware Unavailability: A kind of sofware risk where the needed hardware specifically needed of a certain project is not available on a certain schedule that is set that it would be use.

e.) Configuring the Project: This simply means that the project might be in jeopardy once the congifure is mistaken and there will be a great need for the project to reconstruct it again.

IDENTIFY RISKS MANAGEMENT STRATEGIES

Risk management is the identification, assessment, and prioritization of risks followed by coordinated and economical application of resources to minimize, monitor, and control the probability and/or impact of unfortunate events. In such cases, there are strategies or techniques as for to guide on how to deliberate certain risks.Identify, characterize, and assess threats.Assess the vulnerability of critical assets to specific threats.Determine the risk (i.e. the expected consequences of specific types of attacks on specific assets).Identify ways to reduce those risks.Prioritize risk reduction measures based on a strategy

What is Computer-Aided Software Engineering?

Computer-Aided Software Engineering (CASE), in the field of Software Engineering is the scientific application of a set of tools and methods to a softwarewhich is meant to result in high-quality, defect-free, and maintainable software products.^[1] It also refers to methods for the development of information systemstogether with automated tools that can be used in the software development process.

The term "Computer-aided software engineering" (CASE) can refer to the software used for the automated development of systems software, i.e., computer code. The CASE functions include analysis, design, and programming. CASE tools automate methods for designing, documenting, and producing structured computer code in the desired programming language.^[3]

Two key ideas of Computer-aided Software System Engineering (CASE) are:

• the harboring of computer assistance in software development and or software maintenance processes, and
• An engineering approach to the software development and or maintenance.

Some typical CASE tools are:

• Configuration management tools
• Data modeling tools
• Model transformation tools
• Program transformation tools
• Refactoring tools
• Source code generation tools, and
• Unified Modeling Language

CASE tools are a class of software that automates many of the activities involved in various life cycle phases. For example, when establishing the functional requirements of a proposed application, prototyping tools can be used to develop graphic models of application screens to assist end users to visualize how an application will look after development. Subsequently, system designers can use automated design tools to transform the prototyped functional requirements into detailed design documents. Programmers can then use automated code generators to convert the design documents into code. Automated tools can be used collectively, as mentioned, or individually. For example, prototyping tools could be used to define application requirements that get passed to design technicians who convert the requirements into detailed designs in a traditional manner using flowcharts and narrative documents, without the assistance of automated design software.

Existing CASE Environments can be classified along 4 different dimensions :

1. Life-Cycle Support
2. Integration Dimension
3. Construction Dimension
4. Knowledge Based CASE dimension

REF:http://en.wikipedia.org/wiki/Case_tools#CASE_tools

What is Software Engineering?

Software engineering is the application of a systematic, disciplined, quantifiable approach to the development, operation, and maintenance of software, and the study of these approaches; that is, the application of engineering to software.

The term software engineering first appeared in the 1968 NATO Software Engineering Conference and was meant to provoke thought regarding the current "software crisis" at the time. Since then, it has continued as a profession and field of study dedicated to creating software that is of higher quality, more affordable, maintainable, and quicker to build. Since the field is still relatively young compared to its sister fields of engineering, there is still much debate around what software engineering actually is, and if it conforms to the classical definition of engineering. It has grown organically out of the limitations of viewing software as just programming. "Software development" is a much used term in industry which is more generic and does not necessarily subsume the engineering paradigm. Although it is questionable what impact it has had on actual software development over the last more than 40 years. The field's future looks bright according to Money Magazine and Salary.com who rated "software engineering" as the best job in America in 2006.

REF:WIKIPEDIA.com