Please answer the following discussion and questions? 1. Discuss the key problem
ID: 3688010 • Letter: P
Question
Please answer the following discussion and questions?
1. Discuss the key problems associated with using packaged software? How can these problems be minimized?
2. End of Module Questions
1. Provide three different options that are available when selecting an identifier for a student entity. What are the pros and cons of each choice? 2. Define what is meant by an entity, attribute, and relationship in a data model. How should they be named? What information about them should be stored in the CASE repository? You may use a table to report your answer, or break it down into entity, attribute, and relationship 3. Summarize the distinctions between the analysis phase and the design phase of the SDLC. 4. Describe the primary activities of the design phase of the SDLC.
Design a database structure that captures/tracks information of researchers within all universities in a given state. Information of interest includes researcher name, title, position; university name, location, enrollments; and research interest. Each researcher can only be associated with one university, and each researcher may have one or more research interest.
3. Answer the following key task.
Task 1: Investigate learning management software packages that are available through application service providers. Using the World Wide Web, identify at least two potential sources of such software. What are the key functions, requirements, pros and cons? Summarize and report your findings. Make sure to include references.
Task 2: Create a request for proposal (RFP) to which interested vendors and consultants could respond.
Reference:
Dennis, A., Wixom, B., & Roth, R. (2012). System Analysis and Design (fifth ed.). Hoboken, N.J.: John Wiley & Sons, Inc.
Explanation / Answer
packaged software --For many years following the introduction of computers to business in the 1950s, corporate IT departments assumed that they would write most of their business software. Larger corporations would hire staff programmers to write corporate information systems, and smaller companies that couldn't afford their own staff would use consultants to create data systems. Gradually packaged software emerged, at first to perform standard corporate functions such as accounting and payroll, and later to do other standardized functions such as purchasing, human resources tasks, and manufacturing. As technology has improved, packages have become more flexible so that they can be adapted to individual businesses, and packaged software is assumed to be suitable for most core business functions.
Disadavantages- packaged software has many bug as they are not customizes and all the packaged software are not fuully tested so that they may have bug on client sides,.
Category
Software Package
Custom Development
Risk
Already tried and tested.
New product carries greater risk.
Team Qualifications
Less expertise is required in analysis, design, and development.
Requires considerable expertise in analysis, design, and development.
Time
Less time is required to implement.
More time is required to complete analysis, design, and development.
Cost
Initial cost is lower.
Initial cost is higher.
Operating Cost
Could be unnecessarily high if not all package features are used.
Corresponds to the nature of the system.
Requirements
Will not fit requirements exactly.
Designed to fit requirements.
Support
Must depend on vendor support and training.
Support and training is provided by the project team.
Documentation
High quality documentation is expected.
Quality of documentation will depend on the skill of the project team writers.
Flexibility
Other related applications are generally easily available.
Other applications must be custom developed.
Obsolescence
Enhancements are provided by the vendor.
Enhancements must be custom developed.
Enterprise Wide Architecture Strategy
. [
May not follow long range objectives and corporate standards exactly; i.e., compromises might be necessary.
Designed in accordance with long range objectives and corporate standards.
entity-An entity may be defined as a thing capable of an independent existence that can be uniquely identified. An entity is an abstraction from the complexities of a domain. When we speak of an entity, we normally speak of some aspect of the real world that can be distinguished from other aspects of the real world.
Attributes- it is the properties of any entity that defin eits features
Relationship- it is key binding between enttiy and attributes.
They are named accourding to the its name convetion. like
entity- bank_customer
attributes- open account , withdraw money, save money etc,
relation- is betwwn account and man;
Answer3- The Analysis Phase is where the project lifecycle begins. The Analysis Phase is where you break down the deliverables in the high-level Project Charter into the more detailed business requirements.
The difference between the two phases is that analysis focuses on determining what the business needs are, whereas the design phase takes those business needs and determines how they will be met through a specific system implementation. The analysis phase includes activities designed to discover and document the features and functions the system must have. In the design phase, those features and functions should not change (much). The focus in design is to figure out how to create a system technically that will provide all those needed features and functions.
The systems development life cycle (SDLC), also referred to as the application development life-cycle, is a term used in systems engineering, information systems and software engineering to describe a process for planning, creating, testing, and deploying an information system
Category
Software Package
Custom Development
Risk
Already tried and tested.
New product carries greater risk.
Team Qualifications
Less expertise is required in analysis, design, and development.
Requires considerable expertise in analysis, design, and development.
Time
Less time is required to implement.
More time is required to complete analysis, design, and development.
Cost
Initial cost is lower.
Initial cost is higher.
Operating Cost
Could be unnecessarily high if not all package features are used.
Corresponds to the nature of the system.
Requirements
Will not fit requirements exactly.
Designed to fit requirements.
Support
Must depend on vendor support and training.
Support and training is provided by the project team.
Documentation
High quality documentation is expected.
Quality of documentation will depend on the skill of the project team writers.
Flexibility
Other related applications are generally easily available.
Other applications must be custom developed.
Obsolescence
Enhancements are provided by the vendor.
Enhancements must be custom developed.
Enterprise Wide Architecture Strategy
. [
May not follow long range objectives and corporate standards exactly; i.e., compromises might be necessary.
Designed in accordance with long range objectives and corporate standards.