DFD Fragments, Diagram Zero and Context Diagram

ItChUrAaNzzz!!!

EXERCISE 1: PERT CHART

EXERCISE 2:Conduct User Training Sessions

Software Risk

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, taken
separately. But if they come together, they become a risk or, in other words, the probability that a disaster will
happen.
Nevertheless, risks can be reduced or managed. If we are careful about how we treat the environment, and if we are
aware of our weaknesses and vulnerabilities to existing hazards, then we can take measures to make sure that
hazards 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 Software Engineering?

Software engineering is 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. Software Engineering is an approach to developing software that attempts to treat it as a formal process more like traditional engineering than the craft that many programmers believe it is. We talk of crafting an application, refining and polishing it, as if it were a wooden sculpture, not a series of logic instructions. The problem here is that you cannot engineer art. Programming falls somewhere between an art and a science.The computer science discipline concerned with developing large applications. Software engineering covers not only the technical aspects of building software systems, but also management issues, such as directing programming teams, scheduling, and budgeting. Software engineering (SE) is concerned with developing and maintaining software systems that behave reliably and efficiently, are affordable to develop and maintain, and satisfy all the requirements that customers have defined for them. It is important because of the impact of large, expensive software systems and the role of software in safety-critical applications. It integrates significant mathematics, computer science and practices whose origins are in engineering.References:1. http://en.wikipedia.org/wiki/Software_engineering2. http://wiki.answers.com/Q/What_is_software_engineering3. http://computingcareers.acm.org/?page_id=12

Computer-Aided Software Engineering-(CASE) Tools

1. Computer-Aided Software Engineering (CASE), in the field of Software Engineering is the scientific application of a set of tools and methods to a software which is meant to result in high-quality, defect-free, and maintainable software products.It also refers to methods for the development of information systems together with automated tools that can be used in the software development process. It can refer also 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.
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 LanguageMany CASE tools not only output code but also generate other output typical of various systems analysis and design methodologies such as:
data flow diagram
entity relationship diagram
logical schema
Program specificatio
SSADM.
User documentation
2. A CASE tool is a computer-based product aimed at supporting one or more software engineering activities within a software development process.
References:
1. http://en.wikipedia.org/wiki/Computer-aided_software_engineering
2. http://www.ask.com/bar?q=what+is+CASE+tool%3F&page=1&qsrc=0&ab=1&u=http%3A%2F%2Fwww.sei.cmu.edu%2Flegacy%2Fcase%2Fcase_whatis.html

House and Lot

Think of all the task that you perform when you purchase a house & lot. Include any research, decisions considerations, or financial issues that relate to the purchase. Draw a Gantt Chart & PERT Chart that shows all the tasks and the estimated duration of each.
(Note: You should come up with a task listing as well as its dependencies.)
PROCEDURES IN PURCHASING A HOUSE.
Get pre-qualified for a loan.
Talk to a Realtor to show you houses.
Make and offer.
Offer accepted.
Open Escrow.
Make Deposit.
Do home inspection. (right after opening escrow)
Ask for a copy of termite inspection.
Ask for copy of all Seller's Disclosure and approve them.
Review home inspection and ask for repairs.
By this point you are probably about 15 to 17 days after acceptance. Make sure you lender already has the unconditional loan approval and knows you are good to go.
Once you know you are approved, have seller do termite work.
5 Days Prior to close of escrow you will do a "Final Walk Through" to make sure your house is in the same or better conditions as when you wrote the offer and that all of the agreed repairs have been done.
Loan will be funded (closed)
Next day the title will be recorded. (escrow is closed)
Usually, seller has 3 days to vacate the house.
Move into your home.
Don't forget to change the utilities under your name.
House Blessing

Who am I

Im Howard James B. Juntilla,Currently Studying at Davao Oriental State College of Science and Technology(DOSCST).A 2nd year BSIT student.

Im just a simple and cute guy. With a simple plan for the future.