Please enable JavaScript.
Coggle requires JavaScript to display documents.
7B Development Strategies (:red_flag:Software development trends (Service…
7B Development Strategies
Software acquisition process
STEP 1: Evaluate the IS requirements
Identify key features (using data from fact-finding)
Consider network web-related issues (run on Internet or Intranet)
Estimate volume and future growth (vd daily orders)
Specify hardware, software or personnel constraints (vd large number of legacy systems)
Prepare a request for proposal (RFP) or quotation (RFQ) (document that specify feature required, RFQ is more specific than RFP)
STEP 2: Identify Potential Vendors or Outsourcing providers, thông qua
Internet
Consulting firm
Forum, newsgroup
STEP 3: Evaluate the alternatives, thông qua
Existing users: lưu ý mostly positive feedback
App testing: try demo copy
Benchmarking: VD measure the time needed to post 1000 sales transactions
STEP 4: Perform C-B analysis
Identify TCO (software license, supplemental maintenance agreement)
STEP 5: Prepare a recommendation
Submit SR documents and deliver presentation
STEP 6: Implement the Solution (c.11)
To complete phase 2, SA must prepare SR documents and presentation
SR documents
(Software requirements specification)
Like a contract show what must deliver to users
Bao gồm: requirements, alternatives, recommendation
Should be easy to read and understand
Presentation to management
Allow time for discussion and Q&A
Start phase 3 (if choose in-house or software package modification)
Logical design: define what must take place, hot how
Physical design: in contrast, is a plan for the actual implementation
:red_flag:Software development trends
Service-oriented architecture (SOA)
Loose coupling
Growth in open-source software
Developers will use more web services
Programmers will continue to use dynamic languages
Culture of DevOps
Cloud as a development platform
Prototyping methods
System Prototyping
Produce a full-featured, working model of the information system and ready for implementation
Design Prototyping (Throwaway Prototyping)
Verify user req, then discard the prototype and implementation continue