Enterprise Mobile Development

How to ensure and develop quality solutions and nip the bugs at the root is an aft discussed problem across product and service companies. Below, is my take on the processes that need to be followed to ensure quality. 1. Write Concise and Effective Use Case Documents with Expected Results and Edge Cases to Test   Every use case should contain: A good name/title, which gives a clear indication of what the use case is all about The goal and description should be clearly mentioned The use case should contain details such as actors, preconditions, postconditions, and triggers It should have the main flow or the steps Any relations to other use cases. For example, included or extended use cases The use case should also mention the alternate or exceptions flow Sometimes, one may not have them and they may not be formatted correctly or a Business Analyst isn’t available to document it. This should, however, not stop the Developers from writing and getting them validated fr...

I was just taking a look at Apache Tika today and because of this I had a chance to brush up my HTML and Regex I used a library called J2HTML   which really made my output easier to handle, Apart from this I used Bootstrap to make my table look neater. I ended up with the below kind of look and feel  The Columns are as below  1. File Name along with the link. \ 2. File Type String  3. Metadata Table - All metadata elements pulled out by Tika 4. Categories - Basically Tags. - Right now it is very rudimentary but will improve it soon - These categories are arrived by analysing the content of the files.  Below is the code that is used to parse a file  Parser parser = new AutoDetectParser(); BodyContentHandler handler = new BodyContentHandler(); Metadata metadata = new Metadata(); FileInputStream inputStream = new FileInputStream(file); ParseContext context = new ParseContext(); Once the above code is executed. han...

                  What is Good Code ? Even if I say nobody cares about your code the quality nonetheless does influence a project. Functional correctness reigns supreme, but if we put that aside what should we look at next? Cohesion and coupling are the two most significant aspects of code impacting software quality. Cohesion Cohesion is how well the bits of a module fit together. A set of functions, an interface, is considered cohesive when each function is closely related to another. For example, drawLine  and  drawCircle  are closely related and belong nicely together in a single  Draw  module. If functions differ in their behavior a module becomes less cohesive. For example,  drawLine  and  calculateBalance  don’t seem to be related at all, So putting them into the same module doesn't make any sense at all.  We can roughly measure cohesion by how simply and pre...

Enterprise Mobility Market – Market Research Analysis Transparency Market Research A recently released report from Transparency Market Research (TMR) forecasts that the global enterprise mobility market will grow at a remarkable CAGR of 24.7% from 2015 to 2022. TMR, a market intelligence firm, states that the global enterprise mobility market, which in 2014 stood at US$86.36bn , is anticipated to reach US$510.39bn by the end of the forecast period.  Radicati Worldwide revenues for the EMM market will total $1,495 million by year-end 2015. This figure is expected to grow to over $4.4 billion by year-end 2019 . This represents an average annual growth rate of over 30% in the next four years. Figure 1, shows the worldwide revenue for the Enterprise Mobility Management market from 2015 to 2019.