Master Index Software - Revision history

Nathanael Wettstein: /* Definitions */

2015-02-21T11:00:13Z

Definitions

← Older revision		Revision as of 11:00, 21 February 2015
Line 20:		Line 20:

	=== Definitions ===		=== Definitions ===
	* Project: An assembly that is treated as an individual project (e.g. Tractor, Power Cube).		The following definitions apply for the software design. The terms used in GVCS so far (and in a future front-end) may differ.
	* Assembly: A major building block (e.g. Tractor, Frame, Grate). Consists of subassemblies or other assemblies.
	* Subassembly: A minor building block, on which (e.g. Tractor, Frame, Grate). Conceptually, the same thing as an assembly.		* Project: An assembly that is treated as an individual project (e.g. Tractor, Power Cube). GVCS: "Machine"
			* Assembly: A major building block (e.g. Tractor, Frame, Grate). Consists of subassemblies or other assemblies. GVCS: "Module"
			* Subassembly: A minor building block, on which (e.g. Tractor, Frame, Grate). Conceptually, the same thing as an assembly. GVCS: "(Sub)Module"
	* Component??		* Component??
	* Part: A minor, atomic part of a (sub)assembly. Will be printed on the BOM.		* Part: A minor, atomic part of a (sub)assembly. Will be printed on the BOM.

Nathanael Wettstein at 10:57, 21 February 2015

2015-02-21T10:57:55Z

← Older revision		Revision as of 10:57, 21 February 2015
Line 18:		Line 18:

	== Specifications ==		== Specifications ==

			=== Definitions ===
			* Project: An assembly that is treated as an individual project (e.g. Tractor, Power Cube).
			* Assembly: A major building block (e.g. Tractor, Frame, Grate). Consists of subassemblies or other assemblies.
			* Subassembly: A minor building block, on which (e.g. Tractor, Frame, Grate). Conceptually, the same thing as an assembly.
			* Component??
			* Part: A minor, atomic part of a (sub)assembly. Will be printed on the BOM.
			* Interface: A description of how two (sub)assemblies depend on each other. An assembly may depend on an interface. Multiple subassemblies may fulfill the interface and are therefore compatible with the assembly.

	=== Sprint #0, 2015-XX-YY ===		=== Sprint #0, 2015-XX-YY ===

Nathanael Wettstein: /* Sprint #0, 2015-XX-YY */

2015-02-18T16:34:56Z

Sprint #0, 2015-XX-YY

@@ Line 24: / Line 24: @@
 Infrastructure
 -------------
-. Sign-up/Login/Logout
+. Sign-up/Login/Logout --> using OpenID
 . Create Organization/Group (OSE would be an Organization).
 . Users can request to join organization, creator of Organization can approve.
@@ Line 37: / Line 37: @@
 . Start a Module Version.
 . Add specific version Module to a specific version of Product.
-. A way to export live tables/diagrams to be embedable in the OSE wiki.
+. A way to export live tables/diagrams to be embeddable in the OSE wiki.
 </pre>
 == Current status ==
 * ...

Nathanael Wettstein: Created page with "== Overview == === Goals === A new software is being created for managing the GVCS modules and versions as defined in Naming and Identification and Master Index. T..."

2015-02-18T16:09:57Z

Created page with "== Overview == === Goals === A new software is being created for managing the GVCS modules and versions as defined in Naming and Identification and Master Index. T..."

New page

== Overview ==

=== Goals ===

A new software is being created for managing the GVCS modules and versions as defined in [[Naming and Identification]] and [[Master Index]].

This software should fulfill these top level user stories:
* As a GVCS developer, I have a central database for the latest machine/module versions.
* As a OSE project manager/product owner, I can judge how this application can be used in combination with the existing databases (dozuki, development spreadsheets, wiki).

The long-term goal is to build a game changing 3D CAD application which is open source and allows real time collaboration.

=== Collaborators ===
For easy referral, some of the collaborators are listed here:
* [[User:Lex Berezhny]]
* [[User:Dorkmo]]
* [[User:Nathanael Wettstein]]

== Specifications ==

=== Sprint #0, 2015-XX-YY ===

<pre>
Infrastructure
-------------
1. Sign-up/Login/Logout
2. Create Organization/Group (OSE would be an Organization).
3. Users can request to join organization, creator of Organization can approve.

Basically similar workflow to GitHub.

Concepts
-------------
1. Create/Edit/Delete a Product: CEB Press
2. Start a Product Version.
3. Create/Edit/Delete a Module: Shaker
4. Start a Module Version.
5. Add specific version Module to a specific version of Product.
6. A way to export live tables/diagrams to be embedable in the OSE wiki.
</pre>

== Current status ==
* ...