k_manager 0.0.13

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: 5e1e2ee281f38810223b80d27b7ed6ba17f6d766c9bc3362925cb781faea6e6f
+  data.tar.gz: cce3bcc06ce095f5f00c55bc60ac47b0ea493930db4ebed635fe106303cf5957
+SHA512:
+  metadata.gz: 7c6154b2a689a193cc88415d89959ca564783b04ee256a74c9a845c3d94102c2ae69be11d47e6cf01cc8e75ca52784d2f4a5b4cb8f373be074112464e7a1da5c
+  data.tar.gz: 70e7121af0c37a4458670b4668e4e8a9f0e4c798e317bca98ccdb27414529b4b7966373f0689a654991eefabdd9af783536aba33691c54b844cc51ade55071c5

data/.github/workflows/main.yml

@@ -0,0 +1,31 @@
+# This workflow will download a prebuilt Ruby version, install dependencies and run tests with Rake
+# For more information see: https://github.com/marketplace/actions/setup-ruby-jruby-and-truffleruby
+name: Ruby
+
+on:
+  push:
+    branches: [ master ]
+  pull_request:
+    branches: [ master ]
+
+jobs:
+  test:
+
+    runs-on: ubuntu-latest
+
+    steps:
+    - uses: actions/checkout@v2
+    - name: Set up Ruby
+    # To automatically get bug fixes and new Ruby versions for ruby/setup-ruby,
+    # change this to (see https://github.com/ruby/setup-ruby#versioning):
+      uses: ruby/setup-ruby@v1
+      with:
+        ruby-version: 2.7.1
+    - name: Install dependencies
+      run: |
+        gem install bundler -v 2.2.5
+        bundle install
+    - name: Run tests
+      run: bundle exec rspec
+    - name: Run rubocop
+      run: bundle exec rubocop

data/.gitignore

@@ -0,0 +1,50 @@
+# Move this into a KLUE SATELITE DOCUMENT
+# See https://help.github.com/articles/ignoring-files for more about ignoring files.
+#
+# If you find yourself ignoring temporary files generated by your text editor
+# or operating system, you probably want to add a global ignore instead:
+#   git config --global core.excludesfile '~/.gitignore_global'
+#
+# The Octocat has a Gist containing some good rules to add to this file.
+#    https://gist.github.com/octocat/9257657
+
+# Ignore Klue Setup.sh
+/bin/runonce/
+k_manager.yml
+
+/_/
+/.bundle/
+/.history/
+/.yardoc
+/_yardoc/
+/coverage/
+/log/
+!/log/.keep
+/doc/
+/pkg/
+/spec/reports/
+/tmp/
+!/tmp/.keep
+*.bundle
+*.so
+*.o
+*.a
+mkmf.log
+
+# Ruby Version
+.ruby-version
+
+# Environment File
+.env
+
+# Gems should not use a Gemfile.lock
+Gemfile.lock
+
+# RubyGem definitions
+*.gem
+
+# rspec failure tracking
+.rspec_status
+
+# ByeBug history
+.byebug_history

data/.rspec

@@ -0,0 +1,3 @@
+--format documentation
+--color
+--require spec_helper

data/.rubocop.yml

@@ -0,0 +1,85 @@
+require: rubocop-rake
+AllCops:
+  TargetRubyVersion: 2.5
+  DisplayCopNames: true
+  ExtraDetails: true
+  NewCops: enable
+  Exclude:
+    - "_/**/*"
+    - "spec/samples/**/*"
+
+Metrics/BlockLength:
+  Exclude:
+    - "**/spec/**/*"
+    - "*.gemspec"
+  IgnoredMethods:
+    - configure
+    - context
+    - define
+    - describe
+    - draw
+    - factory
+    - feature
+    - guard
+    - included
+    - it
+    - let
+    - let!
+    - scenario
+    - setup
+    - shared_context
+    - shared_examples
+    - shared_examples_for
+    - transaction
+
+Metrics/MethodLength:
+  Max: 25
+
+Layout/LineLength:
+  Max: 200
+  # Ignores annotate output
+  IgnoredPatterns: ['\A# \*\*']
+  IgnoreCopDirectives: true
+
+Lint/UnusedMethodArgument:
+  AllowUnusedKeywordArguments: true
+
+Style/Documentation:
+  Enabled: false
+
+Style/BlockComments:
+  Enabled: false
+  Include:
+    - "**/spec/*"
+
+# My Preferences - Start
+Metrics/ClassLength:
+  Enabled: false
+Metrics/ModuleLength:
+  Exclude:
+    - "**/spec/**/*"
+Naming/MemoizedInstanceVariableName:
+  Enabled: false
+Naming/VariableNumber:
+  Exclude:
+    - "**/spec/**/*"
+Style/EmptyMethod:    
+  Exclude:
+    - "**/spec/**/*"
+Metrics/ParameterLists:
+  Exclude:
+    - "**/spec/**/*"
+Layout/EmptyLineBetweenDefs:
+  Exclude:
+    - "**/spec/**/*"
+
+Lint/AmbiguousBlockAssociation:
+  Exclude:
+    - "**/spec/**/*"
+
+Style/AccessorGrouping:
+  Enabled: false
+
+Layout/SpaceBeforeComma:
+  Enabled: false
+# My Preferences - End

data/Assessment1.md

@@ -0,0 +1,127 @@
+1. Business modelling tools and Technical modelling tools
+
+Technical modelling tools 
+ERD
+ 
+- Entity Relationship Diagram used for Databases
+
+Tools: Gliffy, Lucid Charts,   
+
+2. Software development methodologies  
+- Agile/  
+- Waterflow  
+- RAD 
+- Extreme XP 
+- Feature Driven  
+- Scrum
+
+3. Application architecture diagram
+- N-Tier (Layered) vs - Microservices
+- Application Architecture Diagram
+- Integration Architecture Diagram
+- Deployment Architecture Diagram
+- DevOps Architecture Diagram
+- Data Architecture Diagram
+
+4. Software risk analysis
+- Estimates, Scope Creep, Stake holder expectations, Low Stake holder engagement,  
+- Requirements / Use Cases
+-  Abuse or security analysis  
+- Unproven Technology  
+- Choice of Infrustruction
+ 
+- Cloud, Server/On-Premise/Integrations
+- UX Design
+ 
+- Framwork, Accesibility
+- Risk analysis
+ 
+- Code Quality
+ 
+- Anti Patterns,
+ 
+- Poor Architecture
+- Test Design
+ 
+- Data edge cases
+- Static Analysis tools
+ 
+- Linters
+- Pen Testing
+  
+5. Database diagram processes and steps
+- ERD
+- Conceptual model   
+- Purpose of database     
+   - Monolith vs Microservice     
+- Relational, Object/JSON/NoSql Store, Key/Value Store, Event Sourced
+6. Design database process and steps  
+- Normalized tables     
+	- Entities     
+	- Attributes  
+	- Relationships, (1-1, 1-m, m-m)     
+	  - Define cardinality, maximum number of values
+	  - Define ordinality, minimum number of values     
+	  - Lhs can be zero or one or many     
+	  - Rhs can be zero, one or many       
+	  - Referential integrity, constraints, indexes
+7. Implement database database processes and steps  
+- DDL  
+	- create database  
+	- create table     
+		- primary key     
+		- attributes  
+		- create index and constraints  
+		- create foreign key references  
+		- create views   
+8. Principles of database-management systems.  
+
+- Shared collection of related data  
+- Data Modeling  
+- Data Storage    
+- Structured Data    
+- Unstructured Data  
+- Transactions (Local or Distributed)  
+- Referential Integrity  
+- Cardinatlity/Ordinality  
+- Distributed Data  
+- Data Warehouses / Big Data  
+- Relational, Object/JSON Store, Key/Value Stores, Event Sourced
+
+9. Object-oriented programming concepts 
+- Encapsulation, Inheritance, Abstraction, Polymorphism
+
+10. Characteristics of a programming language (C#) 
+- Object Oriented 
+- Memory Management 
+- Garbage Collection 
+- Type Safe 
+- Compiled to Byte Code 
+- Cross Platform  
+11. Open-source development tools and platforms 
+- Git Hub 
+- VSCode 
+- Bootstrap, Material, Tailwind CSS 
+- Angular, React, Vue   
+12. Input and output requirements & examples 
+- Input   
+- Console, Terminal, Browser, Ports, Devices - 
+Output   - Console, Screen, Printer, Devices (3D Printer, Robot), Ports (Database, Message Queue)
+13. Testing techniques 
+- Unit Testing 
+- Integration Test 
+- Regression Testing 
+- Penn Testing 
+- User Acceptance Testing  
+14. Computer hardware & why it is important in soft dev
+ 
+- PC, Mac, Embedded Device, IOT, Mobile (Android, IOS, Tablets) 
+- Operating systems, Kernals, VM's and Dockerization 
+- Provides both a physical devices  and virtual environments on which to run applications  
+15. Computer networking components & why it is important in soft dev 
+- Allows for distributed computing 
+- Scalable databases 
+- Scalable services 
+- Provides redundancy and resilience. 
+- Provides external backup stores
+

data/Assessment2.md

@@ -0,0 +1,88 @@
+# Assessment
+
+Validate Software
+
+ICPTPRG520 Validate an application design against specifications
+
+## PART 1
+
+1. Develop a proof of concept
+2. Present the prototype system
+3. Perform design and code validation
+4. Document and report validation results
+
+A. Determine the procedures and tools required to perform
+
+* Software requirements validation
+* Database validation
+* Software design validation
+* Source code validation
+* User Interface (UI) validation
+* Test validation
+
+B. Now it is time to design and build a prototype.
+1. Identify a prototyping tool to develop proof of concept
+2. Identify the use cases from the software requirements.
+3. Develop a prototype using the selected tool.
+
+C. Save your word-processed document as VDP_Part1
+
+## PART 2
+
+10-15 minutes to present your prototype
+
+Role Play Participants:
+  Client and Developer.
+
+1. Identify each use case requirements that you need to fulfil
+2. Confirm the completeness and correctness of the requirements using appropriate questioning and listening techniques.
+3. Demonstrate the prototype (from Part 1) to the client and determine whether any further refinements need to be made.
+4. Record the outcome of the presentation and any changes required in a document.
+
+## PART 3
+
+Now you have implement selected use cases, its time for you to validate it.
+
+Record your validation details
+- Date
+- Name
+- Procedures
+- Results (including screen shots)
+
+1. Validate the software design to ensure the design is complete, accurate and feasible.
+   1. Include diagrams, class, erd, activity, seq, flow etc...
+2. Validate the database structure and elements, inluding screenshots
+3. Validate the UI design
+4. Validate the software code for consistency and analysis of the code using 2 static analysis tools (c# and web). Include screen shots
+
+## PART 4
+
+Document and report validation results
+See: Original document for this.
+
+### Application Requirements
+
+Sydney club needs a simple membership system.
+
+System should allow club employees to enter member details.
+
+Future: Guests can sign-up and manage their membership online via the clubs website and via mobile app.
+
+## Database
+
+### Users
+
+The users table will hold a list of employees who can add new members to the system.
+
+* email - Valid email that acts as a unique user name
+* password - hashed value that holds the users password
+
+### Members
+
+Members table will store member details
+
+* First name
+* Last name
+* Phone number
+* Date of Birth
+  

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,74 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, gender identity and expression, level of experience,
+nationality, personal appearance, race, religion, or sexual identity and
+orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+- Using welcoming and inclusive language
+- Being respectful of differing viewpoints and experiences
+- Gracefully accepting constructive criticism
+- Focusing on what is best for the community
+- Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+- The use of sexualized language or imagery and unwelcome sexual attention or
+  advances
+- Trolling, insulting/derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+- Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at david.cruwys@bugcrowd.com. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/