Implementation Strategy for Commercial Application Package (Commercial Aplicattion Package)
Many core applications such as HR, finance, business acquisitions, manufacturing, and distribution, there sedilit competitive value in building the system - that's why commercial application package is purchased.
Last komesial solution is ERP or Enterprise Resource Planning. ERP solutions provide all the core information system applications for business overall. Examples, SAP, People Soft, and Oracle Applications.
Basic ideas behind the route implementation of commercial application package are:
• Solution-slusi packaged software denagn should be selected carefully to meet business needs
• The solutions are packaged software is not only expensive to buy, but too expensive to be implemented
• software packages typically must be customized and integrated into the business
• software packages rarely meet all the requirements of the business to satisfy customers
Excellence
• These systems can usually be implemented for the new faster because no extensive programming required
• Many businesses can not afford to provide staff and expertise needed to build their own solutions
• application vendors to spread development costs to all customers their software yangmembeli
• Vendor applications accepted responsibility is a significant improvement of system and error correction
Weakness
• COTS Impkementasi successful depends padakebrhasilan panjangdan term survival of an application vendor.
• A system purchased merfleksikan rarely an ideal solution that businesses can achieve success with a system developed in-house performance is dikustomasiuntuk harapam-management expectations and the appropriate user
• There is at least the refusal to change business processes to adapt the software
Time
Labels
- Film (3)
- Information System (8)
- Lifestyles (1)
- Multimedia (5)
- Networking (7)
- Research Methodology (7)
- Software (4)
My Blog List
-
RA.Kartini16 years ago
Monday, April 26, 2010
Commercial Aplicattion Package
Diposkan oleh
Kelik
di
5:11 PM
0
komentar
Label: Information System
Rapid Application Development Strategy
Rapid Application Development Strategy (Rapid Application Development / RAD)
Is a system development strategy that emphasizes speed of development through extensive user involvement in konsteruksi, fast, bears, and getting a series of working prototypes of a system.
RAD is the basic idea;
1. more actively involve the users in the activity system design, analysis, and construction.
2. organizing the system development into a series of intensive seminars and focused with the users, owners, analysts, designers, and system builders.
3. accelerate the phases of requirements analysis and design through construction approach over and over.
4. shorten the time required.
RAD Excellence
1. useful for projects where the requirements of users is uncertain and imprecise.
2. encouraging active user participation and management.
3. projects have more visibility and support tingg.
4. users and the management view-based solutions software and work faster than pengembanagn-driven model.
5. errors and omission tends untukdideteksi early.
6. testing and training is a natural Additional products from a fundamental approach to prototyping.
7. recurrent approach is a more natural process.
Weaknesses RAD
1. be some people argue that the RAD mentality encourages "codes, implement, and improve."
2. RAD prototype can easily solve problems encountered an issue with the wrong-because the analysis of truncated or diabaikian problems.
3. RAD-based prototype of the analysis may be made inferior to consider alternatives other more technical berniali.
4. emphasis on speed may affect adversely the quality of roads caused by the proposed bypass bad denagn through methodology.
Diposkan oleh
Kelik
di
5:08 PM
0
komentar
Label: Information System
NFORMATION SYSTEM DEVELOPMENT
System development process
System development process is a set of activities, methods, best practices, goods for delivery, and automated equipment used in the steakholder to develop and continually improve information systems and software.
Capability Maturity Model
CMM framework for systems and software designed to help organizations improve the maturity (maturity) the processes of development of their system. CMM is organized into five maturity levels:
- Tingkat1-start: at this level, system development projects do not follow consistent processes. Each team TODD development tools and methods of their own.
- Level 2 - can be repeated: at this level, the project management processes and practices established to track cost schedule, can the functionality of the project ..
- Level 3 - defined: At this level, the standard system development process (metologi) purchased or developed. All projects use a tailored version of this process to develop and maintain information systems and software.
- Level 4 - Managed: At this level, these goals can be measured for quality and productivity was formed.
- Level 5 - optimized. At this level, the process is continuous development of standardized systems, monitored and improved based on measurements and analysis of data ..
Against Lifecycle Methodology
The life cycle is factoring the useful life of a system of information into two stages (1) penegmbanagan system and (2) operation and maintenance sistem.Ada two-stage life cycle which is a key event that triggers a change from one stage to other stages, namely;
1. when the spin system from development to operations and maintenance, a conversion must occur / appear.
2. at a time, obsolescence appears and a rotating system of operation and maintenance to re-thresholded.
FAST is an acronym of Methodology Framework for the Application of Sistems Thinking (Framework for the application of systems thinking). An intelligent framework fleksibeel enough for a lot of similarities denagn book-based methodologies and commercial practices will be found preformance.
BASIC PRINCIPLES OF SYSTEM DEVELOPMENT
• Principle 1: Involve the User System
• Principle 2: Use a Problem Solving Approach
• Principle 3: Establish phases and activities
• Principle 4: Document Throughout Development
• Principle 5: Establish standard
• Principle 6: Process and Project Management
• Principle 7: Information System confirmed as the Capital Investment
• Principle 8: Do not be afraid to cancel or revise scope
• Principle 9: Divide and Conquer
• Principle 10: Design a System for Growth and Change
System Development Process
Development projects driven by a combination of problems. Opportunities, and orders.
Developed a useful framework to classify the problem, namely PIECES;
P: the need to correct or improve performance
I: the need to correct or improve information utnuk
E: the need to correct or improve the economy, controlling
costs, or meningklatkan keutungan
C: the need to correct or improve the control or security
E: the need to correct or improve the efficiency of people and processes
S: the need to correct or improve service to customers, and
others.
Classical Project Phase
Definition of scope.
There are two purposes of the definition of the scope
1. he answered the question, "Is this project worthy of note?"
2. and assume that these issues deserve attention, it determines the sizes and boundaries of the project, the project vision, all restrictions or limits, project participants are required. And finally, budget and schedule.
Diposkan oleh
Kelik
di
5:06 PM
0
komentar
Label: Information System
Architecture Framework for Information Systems
Information system architecture is a framework where the union of various stakeholders with different perspectives can be organized and look at the fundamental building blocks of information systems. Information system architecture serves as a higher level framework for understanding the different views will be fundamental building blocks of an information system.
Oriented information systems perspective this purpose are:
1. aim to improve knowledge of business insights. Knowledge is the product data information.
2. purpose of improving services and business processes.
3. memperbaiaki purpose of business communication and collaboration between people.
Three views are represented in the model.
a. knowledge-knowledge that helps business managers make smart decisions.
b. Process-activity-activities that implement business mission.
c. Communication-How berantar system to face with its users and other information systems.
Knowledge Builders Block
Business knowledge derived from data and information. Through processing, the data is processed to generate information to produce knowledge. Knowledge is what allows the company to achieve the mission and vision.
Knowledge of system owners will view
Business knowledge in the first form of a simple list of entities and deploying business rules, for example, entity-entis bsinis is CUSTOMER, PRODUCT, EQUIPMENT, CONSTRUCTION, ORDER and PAYMENTS. Examples of business rules that are useful for system sales is:
- A customer can assign orders must be determined by the customer.
- An order to sell the products may be sold by the order.
Information generated from the raw data that describe the business entities. Therefore, it makes sense if we have to quickly identify relevant business entities that we must capture and store.
Diposkan oleh
Kelik
di
5:05 PM
0
komentar
Label: Information System
BLOCK DEVELOPMENT Information System
- Product Information System
Understanding of front-office information system itself is an information system that supports the business functions that extends to customers while the back-office organization information system is an information system that supports internal business operations of an organization and also achieved its suppliers.
Classes of Information Systems Applications
Transaction Processing System (Transaction Processing System / TPS).
Management Information Systems (Management Information System / MIS).
Decision Support Systems (Decision Support System / DSS).
Executive Information Systems (Executive Information System / EIS).
Expert System (Expert System).
Communication and Collaboration Systems (Comunication and Collaboration System).
1. Office Automation System (Office Automation System). The first transaction process to respond to input transaction data. This transaction resulted in the transaction information to verify the correct processing of input transactions.
2. The second transaction process menghsilkan output transactions (eg invoices).
3. first management information system to produce reports or sales information.
4. Second management information system using business models to generate operational management informsi.
5. MIS may use data from multiple transactional database.
6. snapshot data from a transactional database data to fill the building.
7. Application of decision support executive information system data will provide a read-only access to the building data to generate decision support and executive management information.
8. An expert system requires a special database that stores the expertise in the form of rules and heuristics.
9. Expert system receives as input a problem or feel the problems in the environment and then processed into a problem with an appropriate solution.
10. Private office automation systems tend to circulate around the needs of individuals will be processing the data and business.
11. Otomatisassi System office work group (working group) is often based message / message-based (or email-based system) and this is a smaller-scale solutions to the needs of the department.
Diposkan oleh
Kelik
di
5:03 PM
0
komentar
Label: Information System
CONTEXT METHOD SYSTEM ANALYSIS and DESIGN
Information system is the arrangement of people, data, processes, and information technology / information technology that interact to collect, process, provide as output information necessary to support an organization. In compiling san Design Framework Analysis System requires:
1. Transaction processing system (TPS) / transaction processing system
Namely: a system of information capture and processing of business transaction data such as orders, attendance card (time card), payment, and reservations.
2. Management information system / management information system (DSS) or decision support system
Namely: system information that helps to identify decision-making opportunities or provide information to assist decision-making.
3. Executive information system (EIS) / information system execution
Namely: a sytem information that supports planning and assessment needs of executive managers.
Expert syste / System ie expert knowledge capture and reproduce the problem-solving experts.
4. Comunication system / system communication and collaboration
Namely: an information system which enables more effective communication between employees, colleagues, customers and suppliers to improve their ability to cooperate.
5 Office automation system / office automation system
Namely: an information system that supports the activities of a business office that provides extensive workflow is improved among the workers.
Diposkan oleh
Kelik
di
5:00 PM
0
komentar
Label: Information System
Sunday, April 25, 2010
Software Quality Criteria
*Efficient utilization of existing computing resources
Capability attribute associated with the level of performance from
Resources used in certain conditions.
*Time Efficiency
Ability of software to process a single command certain functions or perform certain functions on a certain timeframe
*Resource Efficiency
Ability of software to perform specific functions under conditions or the results of certain specific conditions on the use of a number of sources resources.
*Functionality
Attributes that describe specific existence of properties and property certain functions that provide the conditions or the desire of user satisfaction.
*Completeness
Where the quality level of software functions necessary to process to meet user wishes
>>Truth The degree to which all functions have a species? Cation own
>>Security Level of quality where the software can detect and prevent weakness, loss of information and the illegal destruction of data sources power,
>>Compatibility Level of quality which the new software can be installed without changes conditions and working environment by providing the possibility peyiapan and replacement of software.
>>Interopalibitas Level of quality where the software can communicate with easily with other systems and easily for use
*Maintenance.
One attribute that describes the capabilities needed for modification specific.
*Improvement
Level of quality associated with the ability to reorganize mistake or error and correction can be handled with keingginan seuasi user.
>>Development or the ability to Expansion
Quality level of effort required to improve or
memodification of the work or function of the software functionality.
>>Testing
Kualita level of software testing as required for software testing
*Portability
Quality attributes related to the ability of software to transferred from certain envirinmet to another envirinmen
*Dependence on hardware
Level of quality that shows the dependence of software on the device particular hardware. Software should not depend on hardware
>>Independence in software support
Level of software quality will be the drivers on species? devices certain software
>>Capabilities Installation
Level of effort to set the software to achieve conditions particular, at the level where the software can be reused on the other application than just to one original application.
*Reliability
Attributes that describe the ability of software to maintain the level of his performance level in certain circumstances and the range certain time
>>The absence of efficiency
Level of quality where there are no software or are found errors or mistakes that can not detected.
Error or Error tolerance ( Describing the quality level of tolerance limits in which the device software will continue to function without causing an error Direct and indirect damage to user data. In this context termasauk in it is the level of ability operation of existing functions to recovery and back in operation
>>Availability
Describing the quality level of software capability still remain in operation at the time of the faulty system
*Usability
Attributes that describe efforts to use (including preparation the use and evaluation of results) and describe the duties of the usefulness function of the user
*Understanding
Number of users who require extra effort to understand and comprehend software
>>Easy to learn
Describing the quality level of effort required by users to understand the software. Ideal condition is that the effort performed a minimum.
>>Operability
Level of quality that describes the suitability of software goals and objectives as well as describing the use of psychological characteristics users including ergonomic factors such as color, size, sound and so forth.
>>The ability to communicate
Illustrating that the quality level of software designed in accordance with psychological characteristics of the user.
Diposkan oleh
Kelik
di
12:24 PM
0
komentar
Label: Information System
System Development Process
The main thing of this process is knowing the design and analysis system. Like, looking at pictures all the major activities involved in the development of a complete cycle.
System Development Process
Information systems development life cycle found divided into six phases, namely:
1. Planning system
2. Systems analysis
3. Overall system design / conceptual
4. Evaluation and selection system
5. Detailed system design
6. Software Development and
System implementation
7. System Maintenance
Diposkan oleh
Kelik
di
12:12 PM
0
komentar
Label: Information System
Blog Archive
-
▼
2010
(35)
-
▼
April
(34)
- Internet Applications
- Multimedia Applications
- Operating Systems
- SOFTWARE CLASSIFICATION
- Analyzing the MAC Address
- Configuring TCP
- Commercial Aplicattion Package
- Rapid Application Development Strategy
- NFORMATION SYSTEM DEVELOPMENT
- Architecture Framework for Information Systems
- BLOCK DEVELOPMENT Information System
- CONTEXT METHOD SYSTEM ANALYSIS and DESIGN
- Software Quality Criteria
- System Development Process
- Building a Plot and Story
- Camera Terms
- MAKING OF SCRIPT STEPS (SCRIPT)
- Storytelling Triangle
- Human Personality Temperament
- Characterization Multimedia
- SCENARIO
- Three-Dimensional Multimedia
- ANIMATED MAKING PROCESS.
- Routing Basics
- OSI
- LAN System
- Full and half duplex
- Image
- Introduction Types of Protocol
- PROPOSAL
- Overview of Information Technology
- RESEARCH IDEAS
- CIENTIFIC WORKS
- SCIENCE
-
▼
April
(34)