Apllication Desing

Question 1

What is Application Profile?

Answer 1

• describes the application we intend to build
• includes all of our assumptions, requirements, and specifications, project participants, an executive summary, and a project timeline. (Application Sizing)
• to project stakeholders for review, to gain approval for the project before we begin development
• presents the vision and direction for our project.
• template is provided (can be adjusted)

Question 2

What is set to generate an Application Profile?

Answer 2

Project Name, Organization Name, Project Led By, Implementation Methodology, Document Process Images

Question 3

What is set to generate an Specification Document?

Answer 3

• Specifications to Include (select from a list)
• Include Change Log (checkbox)
• Include Accesptance Criteria (checkbox)
• Include Linked Requirements (checkbox)

Question 4

What is set to generate an Application Document?

Answer 4

• Detail Level (High Level Overview, Full Application Documentation, Property references)
• Section headings will display (Rule Name, Short Description)
• Suppress class and ruleset references
• Create links to rule forms within document
• Rulesets (list)
• Case types and supporting specification types
• Document sections
• Case type criteria

Question 5

Documentation wizard steps?

Answer 5

1. Select content: select the contents of the document to be created
2. Define data: define data to use in screenshots
3. Captures screenshots: Take screenshots of the application, using the defined data
4. Order content: Arrange the contents of the document, and add outside material

Question 6

Different detail levels?

Answer 6

• A high-level overview that contains information about case types, flows, user interfaces, requirements, and specifications.
• Full documentation that contains everything in the high-level overview, plus information about secondary rules such as service levels and correspondence.
• A property reference that lists all of the data elements in our solution, organized by case type.

Question 7

Security Requirements attributes?

Answer 7

• rarely represent a functional aspect of the business process
• represent application behaviour
• do not/rarely represent case behaviour
• often classified as non-functional requirements
• can also be described as enterprise-standard requirements. (“Must support two-factor authentication”, “Passwords must be at least 8 characters long”, “Users should be logged on automatically when they access the system”)
• specifications are not logged against a case type
• endered against Security supporting tpye
• Security supporting type is used to document, as security behaviors are applied against the entire application
• specify details such as logon schemes
• specifications categorized under a supporting type are considered part of any case type contained within the application, whereas specifications categorized under a specific case type are considered part of only that case type.
• describe a desired capability of the system
• Security specifications describe how our application satisfies its security requirements (e.g. single-signon authentication through LDAP).
• special requirements should be noted on the appropriate specifications
• specific flows, flow actions, decisions, or any other rules can have special security needs (only the requestor is allowed to update or withdraw a case)

Question 8

Developer Toolbar

Answer 8

• Tracer to trace the execution of an application at runtime with powerful debugging utilities including step-by-step execution, breakpoints, watch variables and customizable event types.
• Clipboard to view the contents of pages stored in memory for a given requestor. Now localizable, the Clipboard has improved navigation, thread selection and editing property values (when appropriate).
• UI Inspector to review the structure of user interface elements in an application. Hover over any element in the Designer Studio to view a live overlay detailing the element’s type and the containing UI rule structure. Use the provided links to open individual rules in the Work Area for closer inspection.
• Performance analyzer to collect system resource usage statistics and gain access to finer grain performance tools such as DB Tracer and Profiler.
• Alerts to view the Alert logs in a human readable format. Alerts are organized into two categories: Performance and Security. Filter alerts that were generated by the current requestor session or all sessions.

Question 9

App design steps

Answer 9

1. Establish a high level project vision
2. Gather and enter requirements
3. Model the process
4. Model the data
5. Design the user interface
6. Automate business logic
7. Connect to external systems
8. Create messages and notifications
9. Add and customize reports
10. Deploy and test the application