1. Software Metric
Software metric is a measure of some property of a bit of software or its determinations, as such metrics are capacities, while estimations are the numbers got by the utilization of metrics. Their motivation is reproducible and quantifiable estimations, acquiring objective, which may have various important applications in timetable and cost estimation, spending plan arranging, software troubleshooting, quality affirmation testing, ideal staff errand assignments and software execution improvement.
2. Robustness of a Software Program
The capacity of software frameworks to respond suitably to anomalous conditions. Strength is the capacity of a framework to forestall, identify, adjust to and recoup from operational issues. Software is strong in the event that it can endure such issues as unforeseen occasions, invalid inputs, defiled inside put away information, shameful utilizations by framework administrators, distracted databases, stress over-burdens etc. Frameworks that incorporate both equipment and software are strong, endure physical issues, for example, gear harm loss of force software accidents and loss of force, software crashes etc.
3. Software Metric for measuring Robustness
|Functional Requirements||Add Event||This system shall allow a user of the system to add an event to their planner||Total/Pre-test check Passed-Failed|
|Modify Event||This system shall allow a user of the system to modify details of an event already in their planner||Total|
|Delete Event||This system shall allow a user of the system to delete an event already in their planner||Total|
|Check Conference Room Planner||This system shall allow a user of the system to view the current availability of any conference room||Total|
|Schedule Meeting||This system shall allow a user of the system to schedule a meeting. This includes inviting attendants and reserving an available conference room||Total|
|Modify Meeting||This system shall allow the scheduler of a meeting to modify its details. If the scheduler is modifying the time and/or location, the system will verify the selected room is available during that time.||Total|
|Cancel Meeting||This system shall allow a scheduler of a meeting to cancel it.
|Organizational Requirements||Deliver Safe, Quality and Reliable Product||Are we achieving expected results?
||N/A||Test Procedure Progress Test Status
|Deliver Products and Services On Time within Budget||Is the program executing on schedule and budget?
Are we meeting technical performance requirements?
Are we producing expected capabilities?
|N/A||-EMV (Project -Office Level)
-CPU Utilization Requirements
-Software Size/Function Points
|Desirable Properties for Robustness||Data Availability||N/A||The degree to which the data required to figure the metric are promptly accessible given the items and procedures at present utilized||-Product Status|
|Productiveness||N/A||The capacity of the software metric to evaluate an imperative ascribe to be acknowledged later on; for administration metrics, the capacity of the metric to give precise software size and exertion gauges; for quality metrics, the capacity at the metric to anticipate software quality|
The degree to which the metric gives criticism so as to influence the result
|-Requirements to Design/Design to Code Traces|
|Validity||N/A||The degree to which the software metric evaluates the ascribes it indicates to quantify; the degree to which it has been observationally tried and bolstered|
|Life Cycle Applicability||The degree to which the metric can be connected all through the SDLC||-Volatility
4. Team Assesment
|Design for Robustness||System cannot handle abnormal situations||System can handle few abnormal situations||System can handle all of the predictable abnormal situations||System can handle all of the predictable abnormal situations and provide feedback to users|
|Search Meeting||System was unable to search meetings properly||System could handle few searches||System could search meetings properly||System could search meetings properly and provide instant results|
|Editing||Editing meetings/event was not being saved||Some meetings were saved and some were not when edited||System could save all the edited meetings||System could save all the edited meetings and provide proper alerts|
|Conference Room Planner||Conference room planner had no proper integration with date & time||Proper integration was applied||System had the capability to confirm or cancel conference room meetings||System can confirm or cancel conference room meetings|
|Data Availability||System was unable to handle Accessible data and procedures||System was able to handle a few Accessible data and procedures||System was able to handle all Accessible data and procedures||System is able to handle Accessible data and all procedures|
5. How to Improve Robustness of Team
Team structure is an imperative component conjectured to influence team viability. Team structure influences the way in which the assignment segments are circulated among team members, and in addition team communication and coordination. The team structure that is appropriate for a particular situation to a great extent relies on upon the assignment qualities and assets accessible. For a team of administrators cooperating with various heterogeneous self-ruling vehicles, there are a few approaches to compose the vehicles.
One normal technique is utilitarian association, in which people practice and perform certain parts. For instance, one individual is in charge of looking and someone else is in charge of reacting to targets. The unmistakable errand obligation additionally decreases the requirement for coordination. One noteworthy drawback of utilitarian association is the trouble in moving workload adaptably to separate surprising bottlenecks.
Communication, a critical coordination instrument, impacts the offer of data among team members. Communication identifies with building an exact comprehension of team members’ needs, obligations, and expected activities, which permits them to suspect each other’s needs so that team members can organize adequately. On the off chance that the team members don’t impart adequately, they may not build up an unmistakable comprehension of the circumstance, which may bring about postponed activities, mistakes, and a problematic dissemination of team assets.
Human-operators teams regularly work under vulnerability. One noteworthy wellspring of instability is assignment load. The entry time and sorts of errands are regularly eccentric and adjusting the undertakings and workload among team members can essentially influence results. Errand arranged team development is the issue of framing the most ideal team to finish some undertakings of interest, given some constrained assets. This issue is a key issue for some applications identified with multi-specialists collaboration, e.g., RoboCup salvage team and so forth. Assignment situated team arrangement is the issue of selecting a gathering of specialists, where every operators is described by an arrangement of abilities; the goal is to accomplish a given arrangement of undertakings, where every errand is made exact by an arrangement of capacities important for overseeing it.