Course Topics

1
Course Topics
2
Key Points to Remember Module 2

• Effective systems design should be
• Traced to a customer's requirements
• Assessed for quality against a set of predefined
  criteria for 'good' design
• CWIS systems design focuses on
• Architecture
• Functional Modules
• Interfaces
• Data

3
Module 2, cont.

• There are typically four CWIS systems design
  scenarios
• New system development
• System redesign
• Enhancements
• Maintenance requests
• CWIS program/functional and technical team
  members play interdependent roles in the systems
  design process that require a combination of
  strong communication, business, and technical
  skills

4
Key Points to Remember Module 3

• 4 key components of effective systems design are
• Organizational support
• Effective organizational processes
• Key relationship management
• Collaborative systems design
• Organizational support leads to desired outcomes
  for children and families and for all key
  stakeholders
• Effective organizational processes are both
  project-wide and systems design-specific

5
Module 3, cont.

• Key relationships need to be nurtured
• Inside the CWIS projects span of control
• Outside the CWIS projects span of control
• Collaborative systems design is a
  cross-functional approach involving key
  stakeholders or their representatives
• Two useful collaborative design techniques are
• Requirements elicitation
• Facilitation

6
Key Points to Remember Module 4

• Quality consists of several attributes.
• Usability objectives are key to forming a sound
  user strategy.
• Understanding the tasks that a user is expected
  to perform is essential in validating that the
  usability objectives were met.
• Usability design is an organizational process
  requiring additional investment.

7
Module 4, cont.

• Accessibility is the law.
• Most states/counties have statutes, policies or
  guidelines.
• There are readily available design guidelines.
• Conformance to accessibility standards is
  critical.

8
Module 4, cont.

• Reviews keep tab on requirements and control
  scope.
• Reviews assist in assessing the design product
  and the design process.
• Reviews assist in achieving a high quality end
  product.
• Reviews are both technical and sociological.

9
Key Points to Remember Module 5

• Common threads throughout a project are risk
  management, change control, and managing user
  expectations.
• Regardless of the type of project, IT or
  otherwise, relationships with the project team
  and stakeholders can make or break the
  possibilities for success.

10
Module 5, cont.

• Design starts with Enterprise Architecture - the
  relationship between the business, technology,
  and information.
• Systems Architecture illustrates potential
  tradeoffs in system design.
• In designing a system, collaborate, collaborate,
  collaborate.
• There is no right or wrong design approach. Pick
  one that works for you.

11
Key Points to Remember Module 6

• There is an increased demand for
• model-driven analysis and design tools.
• Model automation drastically improves quality,
  consistency, agility, and productivity.
• UML is the standard for representing software
  models.
• By 2012, demand for a single product with BPA,
  OOAD and Database Design will be the prevalent
  solution.

12
When I Get Back to My Office

• Name 3 to 5 relevant State experiences, samples,
  or references that you can apply to your CWIS
  systems design work when you get back to your
  office.

13
Training Session Evaluations
What went well? How can we improve?