Æ



 
 
P
d


Æ



 for the ICANDO Chemicals system (to the original table are added

  and 
 as stakeholders):

Æ
  
   

 
 


£se of interface
prototype evaluations
The new system
£se the new order-processing and feedback;
should be usable and
system to process orders Employ best design and
user-friendly
implementation
techniques.

Call centre staff may Agreements on training

need training schedule and budget

  
New personnel may Agreements on
need to be recruited recruiting

Provide detailed operational The new system Business analysis to

knowledge of order processing needs to capture focus on call centre staff
and consult customers on operational
acceptability and requirements knowledge

Planning of a new distribution

 scheme and changing if
necessary warehouses and
distribution
Develop professional
purchasing approach
Crucial that this is
timely achieved and Develop supplier
effective relationships and
ensure good quality
contracts

c
P ag e
d

 
D


  
 





  
 
  


Potential improvement in communication Possible late delivery of the product

between the company and traders

Skepticism expressed by the senior managers

Competition already has such a system

High initial investment cost requirement

Increase of usability and ease of access for traders

Potential ease of tracking risk in busy times

Æ


  
 





Æ   

c‘ The development of a trader͛s workbench will facilitate the communication between the
company and traders.
ñ‘ A trader͛s workbench will make reporting, data analysis and record management for the
middle management easier. It will enable managers see the portfolios of all the traders and
to access and forecast the overall risk of the trading floor. It will also facilitate the creation
of spending and profits reports.
‘ It will give systematized information on planned and future stocks and production capacity
to the traders.
‘ ICANDO Oil Trading already has a good existing IT infrastructure and various well-developed
Web sites. There is a capacity to host the software, so the addition of the workbench should
not be a problem.


 

c‘ There is a possibility of late delivery of the product.

ñ‘ Senior management has already expressed skepticism for the development of a workbench.
Thus, there may be a potential damage to staff relationships.
‘ High initial investment cost may be required for the development of the workbench.

    

c‘ A trader͛s workbench with make the risk management easier.

ñ
P ag e




c‘ If the workbench is not delivered in good condition and implemented on time, the company
will apparently lose money and the traders trust in the company may decrease.

P

Æ
 Æ

 


Æ 
       Æ
    



  
Æ 
     c

 


 ʹ determining the needs 

ͶDetermining if the proposed
and expectations of the stakeholders, defining development is worthwhile.
what the system should do and defining the



ͶDetermining if there is a
system performance in terms of reliability, number potential market for this product.
of people using it and quality  ͶDetermining what functionality
the software should contain.
 
 ͶObtaining the
requirements from the user.




ͶDetermining what tasks and
structures are common to this problem.
Æ
 


 ʹ Defining the behavior of the  
 ͶDetermining how to develop
computer system and creating G


 
  the software.


 




. 


ͶDetermining cost estimates.
Æ ͶBuilding a schedule for the
development.
Æ 
 



ͶDetermining
activities that will help ensure quality of the
product.

   ͶDetermining the
subtasks necessary to develop the product.
 ʹ Determining how the software will  ͶDetermining how the software should
operate and decomposing the system into provide the functionality.
manageable parts that can be developed and   
  ͶDesigning the structure of
deployed. Creating 

     

  the system.


 
 
 .  
  ͶSpecifying the interfaces
between the parts of the system.

  ͶDesigning the algorithms for the
individual parts.
 
 ʹ Building the software  
 ͶBuilding the software.

   - Executing the software with data to

  ͶExecuting the software with data to
ensure that the software works correctly. Provide ensure that the software works correctly.
feedback to the development team on the quality     ͶTesting by the original developer.
of the product. Integration testingͶTesting during the integration


P ag e
 of the software.
Æ
    ͶTesting the software in an
environment that matches the operational
environment.
 
  ͶTesting by the customer at the
developer͛s site.

  ͶTesting by the customer at the
customer͛s site.

   ͶTesting to satisfy the
purchaser.
   ͶSaving tests from the
previous version to ensure that the new version
retains the previous capabilities.
 
  Releasing and installing/activating 
ͶProviding the customer with an
the product. effective software solution.
 

 ͶMaking the software available at the
customer͛s operational site.


  ͶTeaching the users to use the software.
 ͶAnswering questions of the user.

 
  £pdating and improving the
 
Ͷ£pdating and improving the
software to ensure continued usefulness. software to ensure continued usefulness.

From the table above we can notice that the stages in the SDLC (Software development life cycle) as
described in both books are generally the same. They both consist of the following main phases:

x‘   
 
 - Project planning and feasibility study

x‘ 
  
 - System analysis and requirements
x‘  
 - Systems design
x‘   
 - System implementation
x‘
   
 -Testing and integration
x‘  
 
 - Software installation
x‘
 
 
 - Software maintenance (which also involves the Disposal phase ʹ
removing of obsolete data)

I personally like both ways of describing the stages in a SDLC. The first one (in our book) is more
concise and ͞practically͟ oriented as for each stage the purpose of the stage, the inputs and the
outputs of the stage and the methods employed in the stage are stated. The second way is more
descriptive and gives idea of the precise sub-stages a software developer has to go through.


P ag e
 Æ

 
 
 
P 


 
 ñ
Aim is to get all of the order taking and order administration implemented.

  
      
     
 

 


 

*  Order taking, Order amendment, Order cancellation, Stock reservation, Delivery
scheduling
Æ
 Production reservation, Credit checking

 Order overview, Web ordering by customer, Web amendment by customer, Web
order tracking by customer
  Delivery confirmation, Delivery rescheduling, Discount calculation, Production
optimization, Delivery optimization, Customer contact history, Special offers
prompting, Call transfer

P 
 

    
      
  

  

Analysis Design Development Testing 2 months

 
 c

Analysis Design Development Testing 4 months

 
 ñ

6 months
 
  Analysis Design Development Testing

Software

î
P ag e
The project has to be finished in 6 months = 24 weeks. There are going to be 3 iterations, and each of
the iterations will last 8 weeks. Each iteration phase will be 2 weeks long. Each   (iteration) will
consist of 4 stages - 

    

  . Three teams will collaborate.

Analysis is executed by a 
 


  and ends with a prioritized list of requirements to be built in
this iteration along with a high-level design. The  
 develops the code for implementing the
requirements and performs the testing. The tested code is handed over to the  
 
 which
performs the final testing and then installs the system for production use.

The board is acting as the steering group. Board meetings are conducted every month and the project
manager is obliged to present the progress. The project manager and the IT director meet every week to
discuss the risk register and the progress of the product. After each successful iteration the IT director
makes a demonstration of the progress so far.

Having in mind the statements above, we are going to have the first software delivery in 8 weeks. The
subsequent one will be in 10 weeks. Definitely by the 4th month there will be enough progress to
convince the skeptical management team that the project is going fine. At the 6th month there will be a
workable and tested release of the software product.

ë
P ag e