Wednesday, September 23, 2009
Wednesday, August 26, 2009
Sunday, August 23, 2009
What is Risk??
1. Risk is a probability that some adverse circumstance will occur
a. Project risks affect schedule or resources.
b. Product risks affect the quantity of performance of the software being developed.
c. Business risks affect the organization developing or procuring the software.
2. SOFTWARE RISKS:
a. Staff turnover
- it affects the project.
- Experienced staff will leave the project before it is finished.
b. Management change
- it affects the project.
- There will be a change of organizational management with
different priorities.
c. Hardware unavailability
- it affects the project.
- Hardware that is essential for the project will not be
delivered on schedule.
d. Requirements change
- it affects the project and the product
- There will be a larger number of changes to the requirements
than anticipated.
e. Specification delays
- it affects the project and the product.
- Specifications of essential interfaces are not available on schedule.
3. Risk Management Strategies
Risk: Organizational financial problems
Strategy: Prepare a briefing document for senior manage-
Risk: Organizational financial problems
Strategy: Prepare a briefing document for senior manage-
problems ment showing how the project is making a very
important contribution to the goals of the
business.
Risk: Recruitment problems
Strategy: Alert customer of potential difficulties and the
Risk: Recruitment problems
Strategy: Alert customer of potential difficulties and the
possibility of delays, investigate buying-in
components.
Risk: Staff illness
Strategy: Reorganize team so that there is more overlap
Strategy: Reorganize team so that there is more overlap
of work and people therefore understand
each other jobs.
Risk: Defective components
Strategy: Replace potentially defective components with bought-in components of known reliability
Risk: Requirement changes
Strategy: Derive traceability information to asses requirements change impeact, maximze information hiding in the design.
Risk: Organizational restructuring
Strategy: Prepare a briefing document for senior management showing how the project is making a very important contribution to the goals of the business.
Risk: Database performance
Strategy: Investigate the possibility of buying a higher-performance database.
Risk: Underestimated development time
Strategy: Investigat buying components, investigate use of a program generator.
4. Before making a decision, we must first consider the consequences of it. If I were on this situation, I will accept the demand from my manager, and would not involve my project team to work with me because I know, they all have young children, and I must consider first their families' sake that myself. I am asked by a manager, therefore, i should have to obey him. Although I will work unpaid overtime, it's quite alright, because software analyst should do his duties and responsibilities on time without a doubt, and without making anyone involve especially that person have some priorities to be considered above all.
Risk: Defective components
Strategy: Replace potentially defective components with bought-in components of known reliability
Risk: Requirement changes
Strategy: Derive traceability information to asses requirements change impeact, maximze information hiding in the design.
Risk: Organizational restructuring
Strategy: Prepare a briefing document for senior management showing how the project is making a very important contribution to the goals of the business.
Risk: Database performance
Strategy: Investigate the possibility of buying a higher-performance database.
Risk: Underestimated development time
Strategy: Investigat buying components, investigate use of a program generator.
4. Before making a decision, we must first consider the consequences of it. If I were on this situation, I will accept the demand from my manager, and would not involve my project team to work with me because I know, they all have young children, and I must consider first their families' sake that myself. I am asked by a manager, therefore, i should have to obey him. Although I will work unpaid overtime, it's quite alright, because software analyst should do his duties and responsibilities on time without a doubt, and without making anyone involve especially that person have some priorities to be considered above all.
5. As for me, in accepting this job, I think it is much better if I will be a project manager in the software project and at the same time, a programmer. Because programmers were not only be the one who plan the development of the software project, but also the project managers. Furthermore, it's also regretting for myself that I would not apply what I have learned from the training on Java Programming, therefore, I f i should accept this job, I prefer to have two tasks concurrently, a project manager and a programmer as well.
Wednesday, August 12, 2009
Monday, August 10, 2009
What is CASE Tools???
CASE is the use of computer-based support in the software development process.
This definition includes all kinds of computer-based support for any of the managerial, administrative, or technical aspects of any part of a software project.
What Is a CASE Tool? Since the early days of writing software, there has been an awareness of the need for automated tools to help the software developer. Initially the concentration was on program support tools such as translators, compilers, assemblers, macro processors, and linkers and loaders. However, as computers became more powerful and the software that ran on them grew larger and more complex, the range of support tools began to expand. In particular, the use of interactive time-sharing systems for software development encouraged the development of program editors, debuggers, code analyzers, and program-pretty printers.
As computers became more reliable and in greater use, the need for a broader notion of software development became apparent. Software development came to be viewed as:
A large-scale activity involving significant effort to establish requirements, design an appropriate solution, implement that solution, test the solution's correctness, and document the functionality of the final system.
A long-term process producing software that requires enhancement through out its lifetime. The implications of this are that the structure of the software must enable new functionality to be added easily, and detailed records of the requirements, design, implementation, and testing of the system must be kept to aid maintainers of the software. In addition, multiple versions of all artifacts produced during a project must be maintained to facilitate group development of software systems.
A group activity involving interaction among a number of people during each stage of its life. Groups of people must be able to cooperate, in a controlled manner, and have consistent views of the state of the project.
This view of "programming in the large" resulted in a wide range of support tools being developed. Initially, the tools were not very sophisticated in their support. However, two important advances had the effect of greatly improving the sophistication of these tools:
Research in the area of software development processes gave rise to a number of software design methods (e.g., Jackson Structured Programming, the Yourdon Method) that could be used as the basis for software development. These methods were ideally suited to automated tool support in that they required step-by-step adherence to methods, had graphical notations associated with them, and produced a large number of artifacts (e.g., diagrams, annotations, and documentation) that needed to be recorded and maintained.
.....personal workstations and personal computers. These machines have relatively large memory storage capacities, fast processors, and sophisticated bit-mapped graphics displays that are capable of displaying charts, graphical models, and diagrams.
We refer to all of the above tools as CASE tools and posit the following definition:
A CASE tool is a computer-based product aimed at supporting one or more software engineering activities within a software development process.
Other authors have attempted to make finer-grained distinctions between differ ent classes of CASE tools along a number of dimensions. The most common distinctions are:
Between those tools that are interactive in nature (such as a design method support tool) and those that are not (such as a compiler). The former class are sometimes called CASE tools, while the latter class are called development tools.
Between those tools that support activities early in the life cycle of a soft ware project (such as requirements and design support tools) and those that are used later in the life cycle (such as compilers and test support tools). The former class are sometimes called front-end CASE tools, and the latter are called back-end CASE tools.
Between those tools that are specific to a particular life-cycle step or domain (such as a requirements tool or a coding tool) and those that are common across a number of life-cycle steps or domains (such as a documentation tool or a configuration management tool). The former class are sometimes called vertical CASE tools, while the latter class are called horizontal CASE tools.
Reference: http://www.sei.cmu.edu/legacy/case/case_whatis.html
This definition includes all kinds of computer-based support for any of the managerial, administrative, or technical aspects of any part of a software project.
What Is a CASE Tool? Since the early days of writing software, there has been an awareness of the need for automated tools to help the software developer. Initially the concentration was on program support tools such as translators, compilers, assemblers, macro processors, and linkers and loaders. However, as computers became more powerful and the software that ran on them grew larger and more complex, the range of support tools began to expand. In particular, the use of interactive time-sharing systems for software development encouraged the development of program editors, debuggers, code analyzers, and program-pretty printers.
As computers became more reliable and in greater use, the need for a broader notion of software development became apparent. Software development came to be viewed as:
A large-scale activity involving significant effort to establish requirements, design an appropriate solution, implement that solution, test the solution's correctness, and document the functionality of the final system.
A long-term process producing software that requires enhancement through out its lifetime. The implications of this are that the structure of the software must enable new functionality to be added easily, and detailed records of the requirements, design, implementation, and testing of the system must be kept to aid maintainers of the software. In addition, multiple versions of all artifacts produced during a project must be maintained to facilitate group development of software systems.
A group activity involving interaction among a number of people during each stage of its life. Groups of people must be able to cooperate, in a controlled manner, and have consistent views of the state of the project.
This view of "programming in the large" resulted in a wide range of support tools being developed. Initially, the tools were not very sophisticated in their support. However, two important advances had the effect of greatly improving the sophistication of these tools:
Research in the area of software development processes gave rise to a number of software design methods (e.g., Jackson Structured Programming, the Yourdon Method) that could be used as the basis for software development. These methods were ideally suited to automated tool support in that they required step-by-step adherence to methods, had graphical notations associated with them, and produced a large number of artifacts (e.g., diagrams, annotations, and documentation) that needed to be recorded and maintained.
.....personal workstations and personal computers. These machines have relatively large memory storage capacities, fast processors, and sophisticated bit-mapped graphics displays that are capable of displaying charts, graphical models, and diagrams.
We refer to all of the above tools as CASE tools and posit the following definition:
A CASE tool is a computer-based product aimed at supporting one or more software engineering activities within a software development process.
Other authors have attempted to make finer-grained distinctions between differ ent classes of CASE tools along a number of dimensions. The most common distinctions are:
Between those tools that are interactive in nature (such as a design method support tool) and those that are not (such as a compiler). The former class are sometimes called CASE tools, while the latter class are called development tools.
Between those tools that support activities early in the life cycle of a soft ware project (such as requirements and design support tools) and those that are used later in the life cycle (such as compilers and test support tools). The former class are sometimes called front-end CASE tools, and the latter are called back-end CASE tools.
Between those tools that are specific to a particular life-cycle step or domain (such as a requirements tool or a coding tool) and those that are common across a number of life-cycle steps or domains (such as a documentation tool or a configuration management tool). The former class are sometimes called vertical CASE tools, while the latter class are called horizontal CASE tools.
Reference: http://www.sei.cmu.edu/legacy/case/case_whatis.html
Thursday, August 6, 2009
Software Engineering Definition
Software Engineering is a discipline of developing software products. A software product is the complete set of computer programs, procedures, documentation, and date specified for delivery to a customer; development is concerned with all technical and managerial activities necessary to create the product; and carrying out the development effectively means meeting customer requirements within constraints of time, cost and quality.
The sofware engineering concept emerged from workshops conducted by the North Atlantic Teaty Organization (NATO) n 1968 and 1969 to consider what was then described as the "software crisis." Too many software development projects were failing and the failures wre attributed to rapid increases in the scale and complexity of the software concerned. It was recognized that a amore systematic approach to software development was needed and that it shoul be basec on established engineering principles.
Reference: Microsoft Encyclopedia 2003
The sofware engineering concept emerged from workshops conducted by the North Atlantic Teaty Organization (NATO) n 1968 and 1969 to consider what was then described as the "software crisis." Too many software development projects were failing and the failures wre attributed to rapid increases in the scale and complexity of the software concerned. It was recognized that a amore systematic approach to software development was needed and that it shoul be basec on established engineering principles.
Reference: Microsoft Encyclopedia 2003
Monday, August 3, 2009
Who Am I??
“Who am I ? ” We’ve all asked this question at one time or another, sometimes out of mere curiosity but often we quest for the right answer. Try to have reflection in front of the mirror, look at yourself…examine yourself from within until to your outside appearance. By that, you surely could recognize yourself. You will realize that there are something awkward and yet something better in you…as a human being.
Each individual possesses it’s own characteristics, behavior and personality. We can not dictate to someone’s own outlook nor anybody could order us to emulate what he/she has. Each of us has our own way to live life, and it’s all up to us how to manage, control and deal with it.
I am but a first year high school when I first heard this question, “Who am I ?”, a question which at first pronounced me as a ridiculous one. I know this could be funny to share, but I really don’t know why my teacher thought to ask such that funny question to us while we’re already cognizant to ourselves. At first, this question is so simple for me to be answered, it is just like telling my name, age, address and anything which would cover me as who really I am. But then, I realized that behind this question, there is a deep meaning…a question that would take us a time o think…a long time to answer…and a question that is needed to answer together with our self-consciousness.
What and who I am now is just because of my own decision, or shall I say, this could be my fate. Whatever things did people knew about me is quite different from who truly I am. I could say that there were many more things people didn’t knew about me…things that will just remain as a mystery.
I do not have any possessions in this world, diamonds, golds and even talents, but this one thing I assure, I am more fortunate compare to those people who have much riches in this world, because my greatest possession is not those wordly things, but GOD alone. Perhaps, unbelievers would say I am weird…an eccentric person…but this is definitely for sure.
I came from destitute family…a family who is always striving to gain something better, a family that is simple yet elegant in spiritual matter, and a family that is holding constantly in hope that there will be brighter tomorrow. I live in the place wherein remote from modernization, and honestly to say, it’s hard to be in. As a student, I am not living in a boarding house because my parents didn’t allow me. Therefore, I am traveling 45-distance from home (Dawan) to Mati and vice versa. For me, as an IT student, would not be enough to live in the place wherein from high-technologies. Frankly speaking, there were times when I feel inferiority to someone who can have anything what they want because they could live convenient and comfortable..But despite of it, I am still fighting against all odds.
On the other hand, I grown up in a nice way under my parent’s hands…with full of care, good teachings and discipline. I am a kind of woman who is not inclined to mingle with wordly doings…to entertain individuals having a vicious deeds which are against from God’s will. Yeah! I live in an unsophisticated way of life. I am not that perfect in physical appearance which men wanted for a woman. Furthermore, I have no good personality to be proud of to my friends, nor an attitudes that would make them belong to my world, but then, there is something in me that people did not acknowledge yet…I am like a shell, living in a confinement...undiscovered. Ascertain if only there is someone who wanted to discover. I could say that I am peculiar…a queer. But then, there is also something in me which I, myself can be proud of…not that in a common ones, instead, in a distinct sense.
Perhaps, few would interested to know further about me, but many would care not. What are those happenings in my life are only me and my God know and share about it. No more…no less.
Each individual possesses it’s own characteristics, behavior and personality. We can not dictate to someone’s own outlook nor anybody could order us to emulate what he/she has. Each of us has our own way to live life, and it’s all up to us how to manage, control and deal with it.
I am but a first year high school when I first heard this question, “Who am I ?”, a question which at first pronounced me as a ridiculous one. I know this could be funny to share, but I really don’t know why my teacher thought to ask such that funny question to us while we’re already cognizant to ourselves. At first, this question is so simple for me to be answered, it is just like telling my name, age, address and anything which would cover me as who really I am. But then, I realized that behind this question, there is a deep meaning…a question that would take us a time o think…a long time to answer…and a question that is needed to answer together with our self-consciousness.
What and who I am now is just because of my own decision, or shall I say, this could be my fate. Whatever things did people knew about me is quite different from who truly I am. I could say that there were many more things people didn’t knew about me…things that will just remain as a mystery.
I do not have any possessions in this world, diamonds, golds and even talents, but this one thing I assure, I am more fortunate compare to those people who have much riches in this world, because my greatest possession is not those wordly things, but GOD alone. Perhaps, unbelievers would say I am weird…an eccentric person…but this is definitely for sure.
I came from destitute family…a family who is always striving to gain something better, a family that is simple yet elegant in spiritual matter, and a family that is holding constantly in hope that there will be brighter tomorrow. I live in the place wherein remote from modernization, and honestly to say, it’s hard to be in. As a student, I am not living in a boarding house because my parents didn’t allow me. Therefore, I am traveling 45-distance from home (Dawan) to Mati and vice versa. For me, as an IT student, would not be enough to live in the place wherein from high-technologies. Frankly speaking, there were times when I feel inferiority to someone who can have anything what they want because they could live convenient and comfortable..But despite of it, I am still fighting against all odds.
On the other hand, I grown up in a nice way under my parent’s hands…with full of care, good teachings and discipline. I am a kind of woman who is not inclined to mingle with wordly doings…to entertain individuals having a vicious deeds which are against from God’s will. Yeah! I live in an unsophisticated way of life. I am not that perfect in physical appearance which men wanted for a woman. Furthermore, I have no good personality to be proud of to my friends, nor an attitudes that would make them belong to my world, but then, there is something in me that people did not acknowledge yet…I am like a shell, living in a confinement...undiscovered. Ascertain if only there is someone who wanted to discover. I could say that I am peculiar…a queer. But then, there is also something in me which I, myself can be proud of…not that in a common ones, instead, in a distinct sense.
Perhaps, few would interested to know further about me, but many would care not. What are those happenings in my life are only me and my God know and share about it. No more…no less.
Subscribe to:
Posts (Atom)
