Headline

Support a web-based UI

Description

The feature applies when an implementation of the system:Company uses a Web-based user interface subject to execution in a Web browser. Such a Web-based implementation may be a self-contained local implementation or it may rely on distribution such that it accesses remote data and operations on an appropriate server; see Feature:Distribution.

Headline

An imaginary HRMS system

Description

System:Company is an imaginary 'Human resource management system (HRMS)' (i.e., an information system) implementations of which ('contributions') are documented on 101wiki. The system is supposed to model the company structure in terms of employees and possibly the hierarchical structure of departments. Employees are modeled in terms of their names, addresses, salaries, and possibly additional properties. The system is supposed to meet certain functional requirements such as totaling all salaries in the company. The system may also be subjected to non-functional requirements such as persistence or distribution. Features are not collected for the sake of an interesting HRMS system. Instead, features are designed to exercise interesting characteristics of software languages and software technologies. Most features are optional so that contributions have the freedom of choice to focus on features that are particularly interesting for a certain objective of language or technology demonstration.

There are the following features:

• Company: Companies, department, employees
• Total: Total the salaries of employees
• Median: Compute the median of the salaries
• Cut: Cut the salaries of employees in half
• Depth: Compute nesting depth of departments
• COI: Conflicts of interests for employees
• Mentoring: Associate mentors and mentees
• Ranking: Enforce salary to correlate with ranks
• Singleton: Constrain for a single company
• History: Maintain and analyze company history
• Serialization: De-/serialize companies
• Persistence: Persist companies
• Mapping: Map companies across technological space
• Distribution: Distribute companies
• Parallelism: Total or cut in parallel
• Logging: Log company changes
• Browsing: Browse companies interactively
• Editing: Edit companies interactively
• Restructuring: Restructure companies interactively
• Web UI: Operate on companies in a web browser
• Parsing: Parse companies in concrete syntax
• Unparsing: Pretty print companies

• Data requirements
  • Feature:Company (XOR)
    • Feature:Hierarchical company
    • Feature:Flat company
  • Feature:COI?
  • Feature:Mentoring?
  • Feature:Ranking?
  • Feature:Singleton?
  • Feature:History?
• Functional requirements
  • Feature:Total?
  • Feature:Cut?
  • Feature:Median?
  • Feature:Logging?
  • Feature:Depth?
  • Feature:Parsing?
  • Feature:Unparsing?
  • Feature:History?
• Non-functional requirements
  • Feature:Serialization? (XOR)
    • Feature:Open serialization
    • Feature:Closed serialization
  • Feature:Persistence?
  • Feature:Mapping?
  • Feature:Distribution?
  • Feature:Parallelism? (OR)
    • Feature:Data parallelism
    • Feature:Task parallelism
• UI requirements
  • Feature:Browsing?
  • Feature:Editing?
  • Feature:Undo-redo?
  • Feature:Restructuring?
  • Feature:Web UI?
• More constraints
  • Feature:Depth => Feature:Hierarchical company
  • Feature:Ranking => Feature:Hierarchical company
  • Feature:History => Feature:Total
  • Feature:History => Feature:Median
  • Feature:Web UI => Feature:Browsing
  • Feature:Editing => Feature:Browsing
  • Feature:Restructuring => Feature:Editing
• Emerging and vanishing features
  • Feature:Reporting
  • Feature:Charting
  • Feature:Grouping
  • Feature:Gender
  • Feature:Bonus
  • Feature:Job description => Feature:Job role
  • Feature:Annual employee review

We use the following informal notation here:

• f? means that the feature f is optional.
• f (OR) means that f is an OR feature; any operands may be chosen, but at least one, unless f is optional.
• f (XOR) means that f is an XOR feature; either of its operands must be selected, but not several of them.
• f1 => f2 means that if f1 is selected then f2 must be selected.
• f (i.e., f with strikethrough) means that the feature is only emerging or already vanishing.

Illustration

The following UML class diagram models the basic structure of the system.

See Theme:Starter for a few very simple contributions in varying languages. These are mostly implementations of the system in varying programming languages, but a UML-based model (as shown above) is also included.

Headline

The capability of distributing programs over computers in a network

Headline

A system for retrieving and presenting Web resources

Headline

Distribute company data and operations

Description

Distribution may be explained with the help of the Client-server architecture. The server is assumed to maintain company data and provide services for data access and behaviors such as totaling or cutting salaries. The client may be, for example, a GUI- or browser-based component through which the data is accessed and the services are invoked by the user. Different kinds of protocols and technologies are conceivable for setting up such a client-server architecture. For instance, client and server could communicate in a request/response manner using, for example, REST. Also, the server may be a SOA-based Web service implying calls to service on the client side. Further, server and client may use RMI to communicate with each other. The feature is considered an execution quality in the sense that the system is observably or knowingly distributed such that the system user interacts with the client whereas some of the operations and some of the data management resides on a different server side.

Headline

A user interface