Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Aalsmeer Flower Auction is an organization that deals with flowers auction market. The
marketplace is located in Netherlands. They have planned to establish online auction market due
to the some threat that threatened their comfortable position. These threats are identify using
Porters five forces analysis. Business and information requirement are also look into, to know
what are the business requirement and information requirement for the online auction market.
After getting to know the business requirement and the information requirement, system
development was evaluate to know which method is appropriate for AFA. Waterfall system
development methodology was chosen as appropriate for AFA due to the business and
information requirement of AFA. Effectiveness of the new system developed was consider on
the organization, management and the employee.
1. Introduction
Aalsmeer Flower Auction (AFA) is an auction house that offer global growers, wholesalers and
exporters a central marketplace in which to trade flowers and plants. New developments in
auction market threatened their comfort ability position, firstly, the need for emergence of
alternative, electronically driven flower markets. Secondly, Retailers asked for fresher products,
more varieties, smaller quantities and multiple deliveries each week. And lastly, merger and
acquisitions among retailers increased their size and power. After studying the case, using the
porter’s five forces, it is realized that AFA has some strength to overcome all these threats. By
this the report suggest to Aalsmeer Flower Auction (AFA) the need to restructure the
organization of the flower market by forming alliance with other business to enable them to have
wider market range.
(www.infoci-journals.com 2005)
Is this Essay helpful? Join OPPapers to read more and access more than 350,000 just like
it!
Porter’s Approach is taken from his 1980 book “Competitive Strategy: Techniques for
Analyzing Industries and Competitors. Porter’s theory has often been used by many
people to understand more about a company’s structure and the method or plan used to
run its business.
In his book, Porter identified 5 external forces that will affect an industry or a market.
The type of forces can help us to understand or to analyze how a company makes its
profits, or how it could attract others to do business with. Porter also helps to identify the
specific company’s competitor.
We may use Porter’s competitive forces to analyze how it can have an impact to the
operations of Cold Storage.
Threat of New Entrants
For the past 30 years, the food industry has seen the up and rising supermarket industries,
which has become dominant in recent years. These large supermarkets focus heavily on
operational efficiency, especially relying on the importance of one stop shopping for
customers,and Cold Storage also operates in such manner. Such method of operation
affects a lot of small traditional shops such as butchers and bakers. This makes it very
difficult and creates a barrier for other new supermarkets to enter this industry. Due to a
large fixed cost and huge capital involved, new entrants’ supermarkets find it hard to
break into the market.
Bargaining Power of Suppliers
The power of the suppliers can be highlighted as they often do business with large food
chains, and also there is a fear of losing these suppliers and their business to other larger
retail supermarket. In Singapore, Giant and Carrefour, as a direct competitor to Cold
Storage, often gets better promotional prices from suppliers, in which we can see that the
smaller retailers cannot compare. In the terms of the suppliers, the huge growing
prospects of these large supermarkets make it difficult for them to source products from
overseas. With this in mind, the suppliers are restricted to operate freely and will...
E-Business
On another plane, developing countries are given increased access to the global
Marketplace, where they compete with and complement the more developed economies.
Most, if not all, developing countries are already participating in e-commerce, either as
sellers or buyers. However, to facilitate e-commerce growth in these countries, the
relatively underdeveloped information infrastructure must be improved.
Supply chain management systems can not only lower inventory costs but can also
deliver the product or service more rapidly to the customer. Supply chain
management can thus be used to create efficient customer response systems that
responds to customer demands more efficiently. An efficient customer response
system directly links consumer.
There are two answers in the literature to these question: synergy and core
competency. The idea driving synergies is that when some units can be used as
inputs to other units, or two organizations can pool markets and expertise, these
relationships can lower costs and generate profits.
How can IT be used strategically here? One use of information technology in these
synergy situations is to tie together the operations of disparate business units so that
they can act as a whole.
Information Partnership
Information Partnership is cooperative alliance formed between two or more
corporations for the purpose of sharing information to gain strategic advantage.
Network Economics
It is model of strategic systems at the industry level based on the concept of a
network where adding another participant entails zero marginal costs but can create
much larger marginal gain.
SPIRAL MODEL
The spiral model [2] was a further improvement on the evolutionary model. It integrates
the concepts of project objectives, risk management, prototyping and project cost to the
evolutionary model. In the spiral model the development is done in cycles of a spiral.
Each cycle starts with determination of objectives, alternatives and constraints for the
cycle. With a good project overview, the objectives of a cycle can be decided. Having the
objectives in place, the next step in a cycle is to evaluate alternatives and identify and
resolve risks. In order to manage the risks involved in a cycle, prototyping, simulation,
benchmarking, etc. are done. Thus the project team is able to zero-in on the best methods
and tools for development. The next step in the cycle is to develop as per the objectives
and methods decided for the cycle. In an early cycle, the development might involve
development of concept of operation or software requirements, whereas in a later cycle it
might mean development of software design, detailed design, or code. Development also
involves validation of the developed output. After development, the last part of the cycle
is to reflect on the work done in the cycle and plan for the next cycle. In an early cycle, it
might be requirements or life cycle plan, whereas later on, it might be an update of earlier
plans (based on the experiences of the cycle), development plan or integration and test
plan. Each cycle has an associated cost. The radial dimension of the spiral is the project
cost and the angular dimension is the project progress for a cycle. The spiral model was a
big improvement as it stressed on evolutionary incremental development, risk
management, prototyping, and project overview and planning.
WATERFALL MODEL
It was understood that software had a life-cycle starting from the decision to make that
software to the time the software was in operation. The term software life-cycle was
based on a basic software process model, indicating the stages software would go through
in its life-cycle. The first response to the software crisis was the discovery of the waterfall
software process model. It was thought that the root cause of the problem was that the
requirements were not understood well enough before the software design and proper
design was not done prior to coding. Applying the engineering paradigm of freezing
requirements before design and freezing design before manufacture, the waterfall model
stipulated that software should be made in a sequential series of stages, like requirements'
analysis, design, detailed design, coding, integration, installation, operations and
maintenance. Slowly, it became apparent that it was not possible to have water-tight
compartments and it was desirable to have feedback between successive stages. Thus a
design error found during coding would lead to a correction of design and then the coding
would continue. This was in line with the engineering practice for a design error found
during manufacture is first corrected in design and than manufacturing is done as per the
modified design. Also, taking the clue from engineering again, it was felt that making a
prototype of the system in early stages would help in understanding the requirements
better and would eventually help in making a better system.
• Print
• AAAAAA
• LinkedIn
• Facebook
• Twitter
• Share This
• RSS
SSADM divides an application development project into modules, stages, steps, and
tasks, and provides a framework for describing projects in a fashion suited to managing
the project. SSADM's objectives are to:
Learn More
In detail, SSADM sets out a cascade or waterfall view of systems development, in which
there are a series of steps, each of which leads to the next step. (This might be contrasted
with the rapid application development - RAD - method, which pre-supposes a need to
conduct steps in parallel.). SSADM's steps, or stages, are:
• Feasibility
• Investigation of the current environment
• Business systems options
• Definition of requirements
• Technical system options
• Logical design
• Physical design
For each stage, SSADM sets out a series of techniques and procedures, and conventions
for recording and communicating information pertaining to these - both in textual and
diagramatic form. SSADM is a very comprehensive model, and a characteristic of the
method is that projects may use only those elements of SSADM appropriate to the
project. SSADM is supported by a number of CASE tool providers.
• Print
• AAAAAA
• LinkedIn
• Facebook
• Twitter
• Share This
• RSS
RAD (rapid application development) is a concept that products can be developed faster
and of higher quality through:
CASE (Computer Aided Software Engineering) technologies are tools that provide the
assistance to the developer in the development of software. Main purpose of the CASE
tools is to decrease the development time and increase the quality of software. Even the
presence of these qualities CASE tools are not being used most often or freely. These
tools are not used freely as they should be; there are some points that need improvement,
so that the use of CASE tools can be increased. No a days most of the software houses
don’t bother to use the CASE tools in their development process. And finally the hurdles
in the promotion of the CASE tools as a standard.
2.0 Introduction
CASE tools reduce the time and cast of software development and ensure the quality of
software. The objective of introducing Computer Aided Software Engineering (CASE)
tools was the reduction of the time, cost of software development and for the
enhancement of the quality of the systems developed (Diane Lending et al. 1998).
1. The time required to develop the software is drastically reduced due to a reduced
requirement analysis business requirements documentation and software
requirement specification) and planning stage.
2. All the software prototypes produced can be kept in a repository for future use.
The reusability of the components also enhances the speediness of the process of
software development.
3. It is much easier for a project manager to be accurate in estimating project costs
which of course means that project cost controls are easier to implement and
manage as well.
4. It is a big cost saver in terms of project budget as well as project time and cost due
to reusability of the prototypes.
5. If a component is being picked for the repository, it is already tested and hence
need not be tested again. This helps in saving time required for testing.
6. The project management requirements are collected in a dynamic manner. Every
time there is a prototype ready, requirements are studied and matched. If there are
any additional requirements, these are then included in the next prototype built.
7. There is a strong and continuous participation of the project sponsor who keeps
giving feedback in the whole process. Hence the end user satisfaction level is
higher when the end result is produced.
8. It promotes better documentation through written test cases.
1. This method may not be useful for large, unique or highly complex projects
2. This method cannot be a success if the team is not sufficiently motivated and nor
is unable to work cohesively together.
3. Success depends on the extremely high technical skills of the developers.
4. There are times when the team ignores necessary quality parameters such as
consistency, reliability and standardization. Hence this can make project quality
management hard to implement during the project management life cycle
Advantages of Prototyping:
Disadvantages of Prototyping: