VM-Core/src/main/java/com/validation/manager/core/server/core/RequirementSpecServer.java
public RequirementSpecNodeServer addSpecNode(String name,
            String description, String scope) throws Exception {
        RequirementSpecNodeServer sns = new RequirementSpecNodeServer(
                new RequirementSpecJpaController(
                        getEntityManagerFactory())
                        .findRequirementSpec(getRequirementSpecPK()),
                name, description, scope);
        sns.write2DB();
        getRequirementSpecNodeList().add(
                new RequirementSpecNodeJpaController(
                        getEntityManagerFactory())
                        .findRequirementSpecNode(sns.getRequirementSpecNodePK()));
        write2DB();
        return sns;
    }
public RequirementSpecNodeServer addSpecNode(String name,
            String description, String scope) throws Exception {
        RequirementSpecNodeServer sns = new RequirementSpecNodeServer(
                new RequirementSpecJpaController(
                        getEntityManagerFactory())
                        .findRequirementSpec(getRequirementSpecPK()),
                name, description, scope);
        sns.write2DB();
        getRequirementSpecNodeList().add(
                new RequirementSpecNodeJpaController(
                        getEntityManagerFactory())
                        .findRequirementSpecNode(sns.getRequirementSpecNodePK()));
        write2DB();
        return sns;
    }
Add a node to this spec.

This is equivalent to a section in a document.

Although database might allow a requirement being on different nodes,
this constraint is imposed via software.

@param name name of new node
@param description description of node
@param scope scope of node
@return Created node.
@throws Exception if errors creating the node occur