Anda di halaman 1dari 2

1. Decide how the new system will operate.

2. Describe the technical details for building the system.


3. This document contains all of the design documents just described: physical process models,
physical data model, architecture design, hardware and software specification, interface design,
data storage design, and program design.
4. The nonfunctional requirements are converted into system requirements that are described in the
document.
5. Document that describes what hardware and software are needed to support the new application.
6. to figure out what the business need.
7. can range from small single-function tools, such as the server-side download manager, to huge
all-encompassing systems, such as enterprise resource planning (ERP) applications that are
installed to automate an entire business.
8. refers to the process of building new systems by combining packaged software, existing legacy
systems, and new software written to integrate these.
9. which means hiring an external vendor, developer, or service provider to create or supply the
system.
10. is a popular term that is essentially an extension of the ASP model.
11. allows developers to be flexible and creative in the way they solve business problems.
12. is very flexible because you agree to pay for whatever time and expenses are needed to get the job
done.
13. the outsourcer reaps some percentage of the completed system’s benefits.
14. if the outsourcer exceeds the agreed-on price, he or she will have to absorb the costs.
15. Employs the people needed to maintain the application.
16. are good alternatives for common business needs.
17. can be used to assist a company with custom development projects and to acquire software
packages.
18. exists for all the functional and technical needs of the system
19. its a formal proposal from a potential vendor, developer, or service provider.
20. is used to determine which vendors have the capability to perform a service. It is often then
followed up with an RFP to the qualified vendors.
21. When a list of equipment is so complete that the vendor need only provide a price, without any
analysis or description of what is needed, the may be used.
22. can be used to organize the pros and cons of the design alternatives so that the best solution will
be chosen in the end.
23. is a custom-built add-on program that interfaces with the packaged application to handle special
needs.

24-34. System Specification Outline

35-36. Project Skills applied during projects


1. Design Phase
2. System Requirements
3. System Specifications
4. Architectural Design
5. Hardware and Software Specification
6. Analysis Phase
7. Package Software
8. System Integration
9. Outsourcing
10. Service as a Service
11. Custom Development
12. Time and Agreement deal
13. Value-Added Contract
14. Fixed-Price Contract
15. ASP
16. Package Software
17. Outsourcing
18. In-House Experience
19. Request for Proposal
20. Request for Information
21. Request for Quote
22. Alternative Matrix
23. Workaround
24. Recommended Acquisition Strategy
25. System Acquisition: Weighted Alternative Matrix
26. Architecture Design
27. Hardware and Software Specification
28. Interface Design
29. Physical Process Model
30. Program Design Specification
31. Physical Data Model
32. Data Storage Design
33. Updated CRUDE Matrix
34. Updated CASE Repository Entries
35. Technical Skills
36. Functional Skills