Carlos Arce

1. Data Information Knowledge Efficient manipulation of data Integration of multiple data sources Cross-links/ references to other resources. 2. Data integrity is data that have a complete or whole structure. All characteristics of the data including business rules, rules for how pieces of data relate dates, definitions and lineage must be correct for data to be complete. Its consequences are serious. They will produce incorrect and inconsistent information. Information systems with poor reputations become serious burdens to the organizations that use them. 3. Changing a relationship from one-to-many to many-to-many in a data model is simply a matter of changing the 1: N notation to N: M. However, once the data has been constructed, loaded with data, and application forms, reports, queries, and application programs have been created, changing a one-to-many relationship to many-to-many means weeks of work. 4. Programs that implement layer-2 protocols use physical addressed, or MAC addresses. Programs that implement layer-3, -4, and -5 protocols use logical addresses, or IP addresses. 5. Public IP addresses are used on the Internet. Such IP addresses are assigned to major institutions in blocks by the Internet Corporation for Assigned Names and Numbers (ICANN). In contrast, private IP addresses are used within private networks and internets. They are controlled only by the company that operates the private network or internet. , there are two versions of IP addresses: IPv4and the newer IPv6. IPv4 addresses look like this one 192.168.2.28. IPv6 addresses are twice as long and are formatted differently. 6. The 5 layers of the TCP/IP-OSU are the following: Application: the application layer governs how two applications work with each other, even if they are from different vendors. Transport: transport layer standards govern aspects of end-to-end communication between two end hosts that are not handled by the internet layer. These standards also allow hosts to work together even if the two computers are from different vendors and have different internal designs. Internet: internal layer standards govern the transmission of frames across a single network- typically by sending them though several routers along the route. Internet layer standards also govern packet organization, timing constraints, and reliability. Data link: data link standards govern the transmission of frames across a single networktypically by sending them through several switches along the data link. Data link layer standards also govern frame organization, timing constraints, and reliability.

Physical: physical layer standards govern transmission between adjacent devices connected by a transmission medium. 7. The four development methodologies are the following: Sdlc: + Comprehensive, addresses both business and technical issues, tried and tested. - Requirements analysis may lead to analysis paralysis, waterfall nature unrealistic. RAD: + Iterative nature reduces risk; JAD improves design, uses of prototypes and CASE tools increases productivity. - Requirements analysis may lead to analysis paralysis, less suited to very large projects. OOD with UP: + Uses cases are effective requirements documents, risk moved forward to elaboration phase, ach iteration terminates with working system. - Less useful for business systems development than for program development, danger of sinking into elaboration black hole. Extreme Programing: + Customer (user) is always involved, paired programming improves quality and reduces risk, most useful when requirements evolve with systems development. - Focus is on programming, JIT can require wasteful redesign, less useful when a system involves many users having different, possibly conflicting, requirements. 8. Systems development is difficult and risky because, many projects are never finished. Of those that are finished, some are 200 or 300 percent over budget. Still other projects finish within budget and schedule, but never satisfactorily accomplish their goals. 9. The five phases of SDLC are the following: System definition Requirements analysis Component design Implementation System maintenance (fix or enhance)