EXPLODED DIAGRAMS

DIAGRAM 0

EVENT RESPONSE TABLE

CONTEXT DIAGRAM

DFD FRAGMENTS

Project Management

1. What is Risk?
---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.

---Risk is defined as "The possibility of suffering harm or loss; danger." Even if we're not familiar with the formal definition, most of us have an innate sense of risk. We are aware of the potential dangers that permeate even simple daily activities, from getting injured when crossing the street to having a heart attack because our cholesterol level is too high. Although we prefer not to dwell on the myriad of hazards that surround us, these risks shape many of our behaviors. Experience (or a parent) has taught us to look both ways before stepping off the curb and most of us at least think twice before ordering a steak. Indeed, we manage personal risks every day.


2. Identify atleat 5 software risk. Discuss each.
Staff Turnover =This software risk can affect the production of the project because after few months all the original programmers have left for more interesting projects or there would be more interesting companies to work with.

Schedule Slips=When the delivery date comes, we have to tell the customer that the software isn't ready as yet and that it may take some more time.

Project Canceled=The customer decides that it would be better to cancel the project

• After numerous schedule slips, he loses confidence that the project can ever be completed.
  
• The Business process changes, which leaves the software incapable of solving the new business problems.

System Goes Sour=The system does go into production (so far so good), but the defect rate or the cost of making changes is so high that the customer looks for other alternatives.

False Feature Rich=The system has great features. Unfortunately these are not the features that the customer finds useful, rather these are the features that the programmer thinks are great features (usually something challenging to accomplish but without any great business value).

Programming For The Future=The system is developed to accommodate features that might be requested by the client at a later stage. Also when the client actually requests the feature (if at all) that we developed, technological changes may have made it cheaper to implement. This leads to greater initial costs.

Frustrated Programmers=Often software development schedules are fixed by the marketing persons in consultation with the client and the schedule is handed over to the programmers to get done. "Ok, guys get this project up and running, you have four weeks to accomplish this". The problem is not that the programmers were not consulted; the problem is that the estimate is not evenly remotely realistic. Often the estimate is as realistic as Clinton's truthfulness or Iraq's WMD. Being asked to meet such unrealistic schedules lead to frustrated programmers, and frustrated programmer don't write great code.

3. Identify risk management strategies.

Pert chart-Problem no. 2

It121-DOSCST-ICSD

What is CASE TOOLS?

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.

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.

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

Many 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

http://en.wikipedia.org/wiki/Computer-aided_software_engineering

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.

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.

http://en.wikipedia.org/wiki/Software_engineering

Who I am?

THIS IS ME! ONLY ME ALONE!
FACING THIS VERY CRUCIAL WORLD...

I'm Krisha Mae M. Pamon. A second year BSIT student.
Hmmm... so weird to say that I'm a kind of girl who wants something extraordinary and finding unusual things in life. I like to be part of the world where I can freely express my thoughts, ideas, emotions and of course myself. But behind this, I'm still a simple girl who wants to live in a simple world.

I love to be with someone who make my world go round! Actually,
I'm not waiting for Mr. RIGHT or MR. NICE GUY. I only need a simple and sincere man whom I can entrust myself and my life. Its the man who will accept the best and the worst that I can be. And who come to love not finding the perfect me but seeing the imperfect me perfectly.

Yes. This is the me:THE real KIXED...

just call me: K-I-X-E-D

K-kind
I-intelligent
X-xtaordinary
but but but but but
E-emotionally
D-devastated

We need companions right?
I am proud to say that I'm part of this very unique group:

"THE ITCHURAANS"
Information
Technology's
Clever
Humorous
Urbane
Religious
Adventurous
Avantgarde
Nebbish
Student

IT121

hahahaha

atlast !!! i have my blog !!!

i can now say: "iboblog Qoh YAN!" ...

:D