Plans the technical infrastructure for the system

Info icon This preview shows pages 31–36. Sign up to view the full content.

View Full Document Right Arrow Icon
Plans the technical infrastructure for the system, including network typology plus hardware, operating system software, and application software on each device Determines how the software components will be assigned to the hardware devices of the system Hardware and software specification - Defines the specific parameters for all hardware and software components in the new system
Image of page 31

Info icon This preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
Software Functions Data storage : structured repository Data access logic : the processing required to access the stored data Data management = Data Storage + Data Access Logic Application logic : the logic documented in the DFDs, use cases, and functional requirements, transforms Presentation logic : the display of information to the user and the acceptance of the user’s commands
Image of page 32
Primary Hardware Components Clients: input-output devices employed by users (e.g., PCs, laptops, tablets, smart phones) Servers: Larger multi-user computers used to store data and run software Network: Connections between clients and servers
Image of page 33

Info icon This preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
Client-Server Architectures Balances the processing between client devices and one or more server devices Servers are responsible for the data access logic and data storage Clients are responsible for the presentation logic A thick client contains all or most of application logic A thin client contains a small portion of the application logic
Image of page 34
Class Exercise Each of these extremes were the “norm” at some point in history and are useful for understanding the issues. In small groups, discuss the architecture strategy: What are the advantages? What are the disadvantages? What can go wrong? Why would you do this? What use scenarios make sense? >>>> TEAM SERVER/THIN <<<<< TEAM CLIENT/THICK
Image of page 35

Info icon This preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
Class Exercise TEAM CLIENT/THICK “SMART PHONE” + UX positive and fast, good performance, not fully dependent on server, less concern about network properties (lag), lower cost for network, moving less over network, customized user experience, more control over resources, better control of data, more secure? Not a central point of failure. More secure, data is local to advice, - high upfront cost, device loss, requires more understanding of how to operate device, higher learning curve, less security? High cost of local fixed issues, required documentation training. Higher possibility of errors/problems , obsolete quickly, TEAM SERVER/THIN “ALEXA” + less storage, less processing locally, access from anywhere, scalable, more secure? Low cost devices, less complex, easy to function, easy to learn, less concern about UI more features, less infrastructure cost, more stable local devices, better manageable of resources (elasticity) , far easier to do complex computations. - network down – screwed! Failure of any part brings whole system down, dependency, high user interactivity a poor choice. Slower response, poor scalability for concurrent users, trust for security, optimized for network performance,
Image of page 36
This is the end of the preview. Sign up to access the rest of the document.

{[ snackBarMessage ]}

What students are saying

  • Left Quote Icon

    As a current student on this bumpy collegiate pathway, I stumbled upon Course Hero, where I can find study resources for nearly all my courses, get online help from tutors 24/7, and even share my old projects, papers, and lecture notes with other students.

    Student Picture

    Kiran Temple University Fox School of Business ‘17, Course Hero Intern

  • Left Quote Icon

    I cannot even describe how much Course Hero helped me this summer. It’s truly become something I can always rely on and help me. In the end, I was not only able to survive summer classes, but I was able to thrive thanks to Course Hero.

    Student Picture

    Dana University of Pennsylvania ‘17, Course Hero Intern

  • Left Quote Icon

    The ability to access any university’s resources through Course Hero proved invaluable in my case. I was behind on Tulane coursework and actually used UCLA’s materials to help me move forward and get everything together on time.

    Student Picture

    Jill Tulane University ‘16, Course Hero Intern